Open TLiu2121999 opened 4 years ago
tirodkar
commented
4 years ago I believe pinning eDO to 1.0.0 in your podfile and making sure EarlGreyApp is added to the application component as well should fix this. Maybe adding your Podfile would help here.
TLiu2121999
commented
4 years ago @tirodkar Please see my changes in podfile and .lock:
Podfile:
Podfile.lock:
TLiu2121999
commented
4 years ago also what do you mean by saying "making sure EarlGreyApp is added to the application component"? @tirodkar
TLiu2121999
commented
4 years ago could you add me to the slack channel or google room please? I'm not able to open either of them
tirodkar
commented
4 years ago eDistantObject is both in the app and test, though the Podfile.lock should apply to both of them. Adding you to the channel.
teddysantyaa
commented
4 years ago hi @tirodkar i'm having this issue as well, is it the same root cause with #971 ?
githubist16
commented
3 years ago hi @tirodkar I am also tracking this issue. can you please add me to the slack channel or google room?
kgpmurray
commented
3 years ago Hi @tirodkar same as above please I have been stuck with this issue for a while
adil-hussain-84
commented
2 years ago This issue is fixed. See this comment in issue #971.
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?