Skip to content

If simulator install ios app failed, reset simulator and try again#733

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 19 commits into from
Nov 11, 2021

Conversation

sunmou99
Copy link
Contributor

@sunmou99sunmou99 commented Nov 3, 2021

Description

Test on Simulator sometimes failed when install iOS app. https://github.com/firebase/firebase-cpp-sdk/runs/4086443522?check_suite_focus=true#step:9:3602

Install testapp: xcrun simctl install 3629D0C4-107A-472E-A79F-A62F60B396DD /Users/runner/work/firebase-cpp-sdk/firebase-cpp-sdk/testapps/auth/integration_test.app An error was encountered processing the command (domain=IXUserPresentableErrorDomain, code=1): This app could not be installed at this time. Failed to load Info.plist from bundle at path /Users/runner/Library/Developer/CoreSimulator/Devices/3629D0C4-107A-472E-A79F-A62F60B396DD/data/Library/Caches/com.apple.mobile.installd.staging/temp.upi3zw/extracted/Payload/integration_test.app Failed to load Info.plist from bundle at path /Users/runner/Library/Developer/CoreSimulator/Devices/3629D0C4-107A-472E-A79F-A62F60B396DD/data/Library/Caches/com.apple.mobile.installd.staging/temp.upi3zw/extracted/Payload/integration_test.app Underlying error (domain=MIInstallerErrorDomain, code=35): Failed to load Info.plist from bundle at path /Users/runner/Library/Developer/CoreSimulator/Devices/3629D0C4-107A-472E-A79F-A62F60B396DD/data/Library/Caches/com.apple.mobile.installd.staging/temp.upi3zw/extracted/Payload/integration_test.app 

Looks like a flakiness in iOS Simulator. Reset and reboot the simulator could possibly solve the issue:
https://stackoverflow.com/questions/40327935/failed-to-load-info-plist-from-bundle


Testing

See the test report in the comments


Type of Change

Place an x the applicable box:

  • Bug fix. Add the issue # below if applicable.
  • New feature. A non-breaking change which adds functionality.
  • Other, such as a build process or documentation change.

@sunmou99sunmou99 added tests-requested: full Trigger a FULL set of integration tests (uses expanded test matrix). and removed cla: yes labels Nov 3, 2021
@github-actionsgithub-actionsbot added tests: in-progress This PR's integration tests are in progress. and removed tests-requested: full Trigger a FULL set of integration tests (uses expanded test matrix). labels Nov 3, 2021
@github-actions
Copy link

github-actionsbot commented Nov 3, 2021

❌  Integration test FAILED

Requested by @sunmou99 on commit 96bfd28
Last updated: Thu Nov 11 13:34 PST 2021
View integration test log & download artifacts

FailuresConfigs
auth[TEST] [ERROR] [iOS] [macos] [ios_target]
messaging[TEST] [ERROR] [Android] [ubuntu, windows] [android_target]

Add flaky tests to go/fpl-cpp-flake-tracker

@sunmou99sunmou99 changed the title If simulator install ios app failed, reset simulator and try to insta…If simulator install ios app failed, reset simulator and try againNov 3, 2021
@sunmou99sunmou99 marked this pull request as ready for review November 3, 2021 22:50
@github-actionsgithub-actionsbot added the tests: failed This PR's integration tests failed. label Nov 4, 2021
@firebase-workflow-triggerfirebase-workflow-triggerbot removed the tests: in-progress This PR's integration tests are in progress. label Nov 4, 2021
@sunmou99sunmou99 added the tests-requested: full Trigger a FULL set of integration tests (uses expanded test matrix). label Nov 4, 2021
@github-actionsgithub-actionsbot added tests: in-progress This PR's integration tests are in progress. and removed tests-requested: full Trigger a FULL set of integration tests (uses expanded test matrix). tests: failed This PR's integration tests failed. labels Nov 4, 2021
@github-actionsgithub-actionsbot added the tests: failed This PR's integration tests failed. label Nov 5, 2021
@firebase-workflow-triggerfirebase-workflow-triggerbot removed the tests: in-progress This PR's integration tests are in progress. label Nov 5, 2021
@sunmou99sunmou99 changed the base branch from main to bugfix/emulator-install-androidNovember 8, 2021 21:49
@sunmou99sunmou99 added the tests-requested: full Trigger a FULL set of integration tests (uses expanded test matrix). label Nov 8, 2021
@github-actionsgithub-actionsbot added tests: in-progress This PR's integration tests are in progress. tests: failed This PR's integration tests failed. and removed tests-requested: full Trigger a FULL set of integration tests (uses expanded test matrix). tests: failed This PR's integration tests failed. labels Nov 8, 2021
@firebase-workflow-triggerfirebase-workflow-triggerbot removed the tests: in-progress This PR's integration tests are in progress. label Nov 9, 2021
@sunmou99sunmou99 added skip-release-notes Skip release notes check and removed tests: failed This PR's integration tests failed. labels Nov 10, 2021
@sunmou99sunmou99 changed the base branch from bugfix/emulator-install-android to mainNovember 10, 2021 00:07
@sunmou99sunmou99 added the tests-requested: full Trigger a FULL set of integration tests (uses expanded test matrix). label Nov 10, 2021
@github-actionsgithub-actionsbot added tests: in-progress This PR's integration tests are in progress. tests: failed This PR's integration tests failed. and removed tests-requested: full Trigger a FULL set of integration tests (uses expanded test matrix). labels Nov 10, 2021
@firebase-workflow-triggerfirebase-workflow-triggerbot removed the tests: in-progress This PR's integration tests are in progress. label Nov 10, 2021
@sunmou99sunmou99 removed the tests: failed This PR's integration tests failed. label Nov 11, 2021
@sunmou99sunmou99 merged commit 96bfd28 into mainNov 11, 2021
@sunmou99sunmou99 deleted the bugfix/simulator-install-ios branch November 11, 2021 19:07
@github-actionsgithub-actionsbot added tests: in-progress This PR's integration tests are in progress. tests: failed This PR's integration tests failed. labels Nov 11, 2021
@firebase-workflow-triggerfirebase-workflow-triggerbot removed the tests: in-progress This PR's integration tests are in progress. label Nov 11, 2021
DellaBitta added a commit that referenced this pull request Dec 1, 2021
* Fix test on emulator workflow failures (#734) * If simulator install ios app failed, reset simulator and try again (#733) * Trigger workflow move github api cod to github.py (#746) * Fix a data race that could manifest as null pointer dereference in FutureBase::Release() (#747) * Cancel callbacks for messaging (#745) * Cancel callbacks for messaging util::Terminate is referenced counted som when there ar more APIs than messaging active the callbacks will not be canceled until later and still cause a NULL ref due to the FutureData being destroyed now. * Cancel callback earlier * Update readme * Remove "Android" tag from the release notes entry for #747 (#749) * Remove calls to LogInfo, LogError, LogDebug during obj-c +load. (#706) * Remove calls to LogInfo, LogError, LogDebug during obj-c +load. This could be causing an issue in C++ as global class constructors have not yet been run. * Add Objective-C/C++ and Java to code formatter script; format those files. (#755) * Allow format_code to format .m/.mm files; clang-format already knows how. * Run format_code.py on all objective-c/objective-c++ files. * Add Java file extensions to format_code.py * Format all Java source files. * Remove check for objc header, as they are now supported. * Format objective-c .h files. * Don't let lint comment on line length any more; code formatting will report that. * Messaging crash during initialization (#760) * Messaging crash during initialization * Update readme * Don't redeclare inherited state in CredentialsProviderDesktop (#731) * Reduce disk space usage when packaging the built SDK (#763) Remove intermediate build files during desktop packaging step. This should reduce the disk space usage, as those files (*.o and *.obj) are not required when merging libraries. * Workaround for Linux x86 build: downgrade libraries on GitHub runners (#764) When installing 32-bit Linux dependencies on GitHub runners, downgrade libpcre2-8-0 to an earlier version to ensure compatibility with the i386 version of the package. This is something that should be fixed in a subsequent Ubuntu release and so is a temporary workaround. This also adds checks to the various prerequisite commands run by build_desktop.py, which was previously just silently ignoring errors (making this much harder to track down). Now it will error out as soon as a command fails. Co-authored-by: Mou Sun <69009538+sunmou99@users.noreply.github.com> Co-authored-by: Denver Coneybeare <dconeybe@google.com> Co-authored-by: Tobias Barendt <tobias@robotsquid.com> Co-authored-by: Jon Simantov <jsimantov@google.com> Co-authored-by: Sebastian Schmidt <mrschmidt@google.com>
@firebasefirebase locked and limited conversation to collaborators Dec 12, 2021
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yesskip-release-notesSkip release notes checktests: failedThis PR's integration tests failed.
3 participants
@sunmou99@jonsimantov@chkuang-g
close