I just upgraded my react-native project to the latest 0.67 version from 0.62 and also gradle from 4.1.0 to 7.1.0 but my app is crashing not even opening after build for release
So I am thinking to create a fresh app with the same package name and then upload again to google play store will google accept it as an update or it will be problematic ?
Please help me i already wasted my 3 days in trying solving crash error .
Related
new to react native expo.
running on
node.js version 16.16.0,
npm verison 8.11.0
expo version 5.4.12 (after running npm install --global expo-cli)
when initiating a new project using
expo init
(choosing blank)
I'm getting a very large project, 190MB!
Looking into the project i see that the reason for that is node_modules,
I tried to set up the env. in 2 different PCs and getting the same thing.
for some reason i cant see any discussions on it,
can someone please tell me what am i doing wrong?
Thank you
node_modules is always a really large folder. It has all the dependencies of your app including the expo and react native libaries. When you build your app for production your actual binary will be a fraction of that. My node_modules folder for a recent React Native app was about 1 GB but the actual app itself ended up only being about 50MB.
Before i continue, let me let you know that i know the code to deply to a targeted build for codepush
appcenter codepush release-react -a aountName/appName -d Production -m --description "CommentHere" -t versionName
I have tried to figure this out on my own and i have not been able to.
I have several versions of my app which i have deploy using CodePush and everything works well but I started having fears of crashes when i installed new packages on the latest build.
This implies the current code base would have new native differences as compaird to the old version.
The question is how can i deploy my new build with new native codes
and packages present to an old version of my app which does not have those
native packages without running into several crashes from all the users using the old version of the app...
I ask this cos i have a feeling if i push the new build with the new changes in UI and native chnages to the old version of my app, the app old app would crash.
If a bug comes in for an old version, how do I fix it and deploy it
for the old version only? Bugs may be critical and not everyone will
have the latest version of the app Or, the bug may only exist on a old
version of the app.
I await your response.
Code push will not affect any native code written within the Android or the iOS projects of a React-Native application. If you read the documentations carefully, it specifically says that it does not change / modify / update the native portion of the app.
Why?
This is because of the way the CodePush mechanism works. In essence, CodePush only stores and triggers the update of the JS bundle of the React-Native application.
This is why we wrap only the JS main app instance with CodePush HOC (Higher Order Component). This is what's happening when you do:
CodePush(MyApp); //wrapping the js bundle at app-root
So, unfortunately in your case, if there are native codes involved, regardless of deployment to a new or old version of the app, it has to be a AppStore / Playstore driven deployment.
I am working on a react native project and I want to connect with firebase ,but when I install firebase its shows that version 8.2.10 is not compatible with the expo package and install 7.9.0. I don't know what to do, please help !
This is the error I am facing.
I am deploying an app built with React Native and Expo to Play Store and the following error appears:
This release is not compliant with the Play 64-bit requirement.
The following APKs or App Bundles are available to 64-bit devices, but they have only 32-bit native code: 1. From 1 de agosto de 2019 all releases must be compliant with the Play 64-bit requirement.Include 64-bit native code in addition to 32-bit native code in your app. Use the Android App Bundle publishing format to automatically ensure that each device architecture receives just the native code it needs.
My Expo version is 27.0.1
Regarding this post https://github.com/facebook/react-native/issues/2814 react-native v0.59 is 64bit compliant (https://facebook.github.io/react-native/blog/2019/03/12/releasing-react-native-059)
and Expo 27 support react-native v0.55.
I'm not an expert with Expo, but can you manually upgrade react-native to v0.59 ? or maybe wait a new version of Expo ?
On July 16th 2019 they stated in 64-Bit Support and Android App Bundles:
We want to let you know that you can now build 64-bit support-enabled .apks that also make use of Android App Bundles (AABs) with SDK33 projects and, of course, with SDK34 upon its release. (Since SDK33 is the first Expo SDK version that uses React Native 0.59, the React Native version that allows for 64-bit support, prior versions of the SDK can’t be updated.)
These updates help us support your new submissions to the Google Play store, which will need to have 64-bit support starting August 1st. Your existing apps won’t need to upgrade to include 64-bit until you need to submit your next app update (though SDK33 has a lot of other fun things you might enjoy!).
Ensure you are running the latest version of expo-cli by running yarn global add expo-cli or npm install -g expo-cli.
Currently, there is no way to fix this. But the Expo Team promised ...
... to add this feature [64-bit binaries] before the deadline.
see here: https://forums.expo.io/t/does-expo-package-64-bit-version/18947
I have an application on App Store with 5.9 build version.But he wants to install it on the above of App store build. I changed my build version from 1.92 to 1.9 and gave him Diawi link . Now he is unable to install Both 1.9 and 1.92 This issue is coming only in iOS 8 and above. I can install the Diawi link to ios 7 and its working perfectly.
Advance th#nx for helping me....
Try enabling TestFlight in your iTunes and share the app with the version you need. I'd recommend you to use Fabric(crashlytics) which takes care of maintaining all the shared app's builds and crash reporting.