Crash happened after upgrading to Earlgrey 2.0 via CocoaPods
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 5.7k
- Forks
- 737
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 5
Description
I upgrated from EarlGrey 1 to 2.0 by changing Podfile, following the doc here:
https://chromium.googlesource.com/external/github.com/google/EarlGrey/+/earlgrey2/docs/cocoapods-setup.md
But after that, every time I build my app, it crashed with these logs:
2020-09-01 12:38:18.726560-0700 Chatter[68904:10543992] Fatal failure: EarlGrey's app component has been launched without edoPort assigned. You are probably running the application under test by itself, which does not work since the embedded EarlGrey component needs its test counterpart present. in /Users/brettfazio/dev/build/EarlGrey/AppFramework/DistantObject/GREYHostApplicationDistantObject.m:96
(lldb)
Should I change any other configurations besides the podfile?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked CocoaPods setup document and the Podfile change described in the report. Reproduce the build and inspect the logged failure in GREYHostApplicationDistantObject.m:96, focusing on the missing edoPort and the requirement for the test counterpart. Done means the upgraded app no longer crashes during launch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, objective-c
- Domain
- mobile, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100