Replies: 1 comment
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am using Expo to build a react native project. I am taking advantage of Expo Updates to push updates OTA. When an update is created it uses the app version (as found in the package.json) to target a "runtime version" - meaning this update will only work for binaries built with that version.
This is fine but when I create a new update on an existing runtime, I also create a new commit and tag incrementing the version as a minor or patch but importantly I cannot and do not update the "version" in the package.json as this would cause the created update to target a new (non-existent) binary runtime version. So I update another key on the package.json; confusingly called "appVersion".
I expose this appVersion as a variable to my code and I want to provide it to RNFB Analytics so that the app_version is set for analytics corectly.
As you can see, I have most users on version 3.0.0, despite having a release for v3.0.1 and I have tested this in debug view and my v3.0.1 is logging as a 3.0.0.
Is there a way to set the app_version manually? I have searched the repo but I cannot find the part which determines the app version.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions