-
-
Notifications
You must be signed in to change notification settings - Fork 344
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
[Question] Code-Push version for both iOS and Android #459
Comments
Hey, so I think this is only an ui problem. Can you confirm this? |
Hello @HazAT, since both the Android app and iOS app have the same bundle ID, they have the same URL, only difference is, again, the code-push release version. Here's my Sentry Project's URL |
I also have issues getting my Code-Push source maps to get linked to their appropriate release, but that might deserve a new issue. |
OK, I see. |
According to the outputs of the code-push cli, the sourmaps are called:
If that is what you meant, then yes, I'm uploading them separately. Closing this issue as I trust your word :) |
OS:
Platform:
Output of
node -v && npm -v && npm ls --prod --depth=0
Config:
I have following issue:
My app has different CodePush releases on Android and on iOS. iOS is ahead by 12 code-push releases. So Android has a label of
v2.1.10-codepush:v23
and iOS hasv2.1.10-codepush:v35
. My question is related to how to handle two different code-push labels for iOS and Android as I have a feeling that Sentry is not separating iOS vs Android when I upload a new source map.In fact, it causes things like these to happen:

In the screenshot above, the last release was made using the Android Code-Push project, and the second one using iOS.
Steps to reproduce:
Actual result:
Expected result:
Imagine the following:
iOS Code-Push is version
v30
, and it's uploaded to Sentry, while Android has a code-push label ofv29
. On the next code-push patch, Android turnsv30
and iOSv31
. This means that if users on iOS don't immediately update the app, their code-push version is stillv30
but if their app crashes, the source map will be linked to the new javascript, which is the equivalent ofv31
on iOS. This would possibly make the stack-trace useless or broken.Any thoughts? Should I just try to have iOS and Android on the same version number to prevent this problem?
The text was updated successfully, but these errors were encountered: