cristianoccazinsp
commented
4 years ago Well, after some work, I've done the following changes so this is really not needed anymore for us, and perhaps for the best.
- Add all important env/version variables to build.gradle and Info.plist
- Read those variables as needed from AppDelegate.m and MainApplication.java and pass them to bugsnag as documented
- Use https://github.com/csath/react-native-config-reader to read those variables into JS so they can be in sync.
Took some work, but I guess it was for the better.
Description
The new
@bugsnag/react-nativeremoved the option to setreleaseStageandappVersionfrom JS. While I understand this makes more sense to be set on the native side, this was a great feature from the JS side.For example, our app has multiple dev environments with the exact same native code but just a different configuration/endpoints, so it doesn't make sense to setup different native build processes just to set this new environment there.
Describe the solution you'd like
Allow
releaseStageandappVersionfrom JS.Describe alternatives you've considered
On android, we need multiple build flavors and manifest files for each one just to set the release stage/app version variables. This is not ideal and adds a lot of work even for building.
Additional context Migrating from the previous version.