Skip to content
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

StreetComplete 33.1 crashes on start #3070

Closed
FloEdelmann opened this issue Jul 15, 2021 · 5 comments
Closed

StreetComplete 33.1 crashes on start #3070

FloEdelmann opened this issue Jul 15, 2021 · 5 comments
Labels
bug feedback required more info is needed, issue will be likely closed if it is not provided

Comments

@FloEdelmann
Copy link
Member

  • LineageOS 17.1 (Android 10)
  • Google Play Store version (via Aurora Store)
  • app version 33.0 worked without crash
  • logcat via Logcat Reader app, filtered by keyword "streetcomplete": logcat_07-15-2021_21-56-55.txt
@westnordost
Copy link
Member

Uff, no way... :-(

Though in the google play console, I can't see this crash even though 5000+ users updated to this version already.

@westnordost
Copy link
Member

So the error means that the app cannot find the resource ic_star_white_shadow_32dp, that's the star shown in the upper left corner. I expect this error to only happen if this resource is really not available in the APK.

I suggest you get the app through Google Play store and see if this solves your issue, not sure what the Aurora Store does.

@westnordost westnordost added the feedback required more info is needed, issue will be likely closed if it is not provided label Jul 15, 2021
@FloEdelmann
Copy link
Member Author

Aurora Store is an open-source reverse-engineered Google Play Store app. You can log into an anonymous or your own Google account and download and install apps from the Play Store.

I just triggered a manual re-download and re-installation of the same app version, and that fixed the issue. It really seems like a one-time issue.

@westnordost
Copy link
Member

Gotta love those heisenbugs

@smichel17
Copy link
Member

I have encountered a similar bug with Aurora Store, for a different app. In that case, it had to do with one of Aurora Store's.. checks ..four methods of installing apks (session installer, native installer, root installer, and aurora services). I believe it was not handling split apk bundles, or whatever Google's new format is, well; switching to a different install method fixed it in my case. I suspect it was the same bug because once I installed the app via the other method (native installer), updates worked fine with the original method (session installer).

(Actually it happened twice, once with Snapchat and once with Lexulous. For the former, I just reverted to an old version that I still had the apk lying around got and stayed there for about a year. For the latter, I finally diagnosed and found it was missing ndk components. Ended up suspecting Aurora Store somehow, tried the other method; when it worked, I dod the same for Snapchat and that worked too).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug feedback required more info is needed, issue will be likely closed if it is not provided
Projects
None yet
Development

No branches or pull requests

3 participants