I am trying to release the React-Native iOS application using Microsoft's Codepush on staging. For this I followed the given instructions on the website and was able to build the bundle file and release successfully on staging but I didn't see the updated changes on mobile which I released.
Firstly I installed the application on mobile using usb (Run on device).
After that I made some changes in my application and released on staging using codepush but when I restarted the app on mobile, it's not showing the changes.
iOS Setup
version: 1.0.0
react-native: 0.17.0
react-native-code-push: 1.5.3-beta
react-native bundle --platform ios --entry-file index.ios.js --bundle-output codepush.js --dev false
code-push release AwesomeProject codepush.js 1.0.0
Can any one help please ? Thanks.
The workflow steps that you posted look correct, so I'm not entirely sure what the issue could be without seeing the logs generated by the CodePush plugin when running your app. If you take a look at our troubleshooting docs, it explains how to examine the logs, along with some common issues and workarounds.
One potential issue is that you're not calling "sync" within the componentDidMount of your root component, and therefore, the plugin thinks your update failed, and rolled it backed. To fix this you simply need to call "CodePush.notifyApplicationReady" in your root component's componentDidMount to notify the CodePush runtime that the update should be considered successful.
Related
React Native app shows error when clicked on debug in Android emulator
Attempt to invoke interface method java.lang.String com.facebook.react.bridge.Cat alystInstance.getSourceURL('on a null object reference
below are error screenshots
Emulator screenshot:
Debugger screenshot:
When clicked on reload app crashes and lost connection to debugger.
Tried uninstalling and reinstalling apk in emulator and cd android ./gradlew clean.
Still same error.
I have faced same issue and it was due to the 'react-native-reanimated' package (It's mentioned in their documentation that remote debugging is no longer possible for react-native-reanimated : React Native Reanimated Known problems and limitations) and the solution is to use flipper to debug : Debugging React Native apps with Flipper
I created an app with expo using the managed workflow, but I now want to eject it so I can build an IPA for IOS. After running expo eject and following the prompts for pod install, when I try to build the app and view it on the simulator in xCode, I get stuck on the splash screen which results in a very long list of errors (attached the relevant looking one below).
Have I missed a step here? I tried looking on the expo documentation but it’s very lacking in using the eject command. Is there a step or something I’m meant to modify after the eject has occurred?
Error: Exception NSException * "expo-updates must be configured with a valid update URL or scope key."
So I resolved this by following these steps after I ejected: https://docs.expo.io/bare/installing-updates/
And also adding the below to the Expo.plist file in the MyApp/Supporting folder with the below:
<key>EXUpdatesURL</key>
<string>https://example.com</string>
I'm trying to test my React Native apk app file.
Here are the steps I made before generate the apk:
react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res
then
cd android && .\gradlew assembleRelease -x bundleReleaseJsAndAssets
I created the key store about a month ago. At that time, I built a AAB to publish to Play Store
I didn't re-generate a new one before doing this
And here's the behavior:
It can't open
I uploaded the apk to a social media app called: Zalo. Then downloaded it to my phone. At first I can't open since the Play Store blocked it. Only when I disabled that ability of Play Service in Settings than I could download it
EDIT 1:
I follow instructions on how to generate the apk from Android Studio, but at the end, it crashes and gives the error:
the transform cache was reset.
EEXIST: file already exists, mkdir 'C:\Users\OKR\Desktop\MeetUp'
I don't know why this happens since I don't have that folder in the Desktop
PLEASE HELP MEEEE
It could mean you already have an app release generated in the destination folder for the new one.
I had the same issue, simply changed my destination folder when exporting through Android Studio and it was solved.
Thank #Iffat for your support. After all I realized that I'm using a key store for debug store. That is indeed the reason why I can't generate my APK
I had to create a new key store for release mode and work on my terminal instead Android Studio . It works.
If anyone encounter the issue, you can read this post here, which was very helpful to me
How to generate a release apk_The right way
I didn't catch since when, but now my xcode crashes if i try to archive my react native ios app.
already did:
project clean & re-download
tried previous success git versions of my app (same: crashes while archiving)
uninstall and install fresh xcode 7.3
disable/enable source control in preferences
so i'm out of ideas now and totally stuck, any help welcome
I developed an application on Apache Cordova, I followed all the steps to generate the .apk to upload on Google Play. I tried many times but Google's response is the same:
We rejected APP, package ID com.xxx.app, for violating our dangerous products policy. If you submitted an update, the previous version of
your app is still available on Google Play. This app uses software
that contains security vulnerabilities for users. Below is the list of
vulnerabilities and the corresponding APK versions that were detected
in your recent submission. Please upgrade your app(s) as soon as
possible and increment the version number of the upgraded APK.
Vulnerability Apache Cordova: The vulnerabilities were fixed in Apache Cordova v.3.5.1.
I have the latest version of Cordova (5.4.1).
The following will detail the steps that I followed for installation and project development:
Start the download of Cordova from the console Node.js using the command npm install -g Cordova.
Install Java: version 1.8.0_65.
Install Android SDK.
Add Java and SDK to PATH.
I downloaded the necessary components of the Android SDK.
Create the project through the commands. (Cordova create Projectxxxx).
Add the Android platform.
I copied my application code in the www folder.
Add the plugins needed for my project: splashscreen and sqlite.
I tested the application on the Android emulator and other mobile phones. All good. Runs perfect.
To create the signed APK file, these are the steps:
-Cordova build --release android. (This generated the android-release-unsigned.apk on platforms / android / build / outputs
/ apk).
-Then, I generated the keystore.
-After the jarsigner.
-Finally: zipalign.
I upload end-app.apk to Google Play.
Another detail that I have is that cordova.js generated version is 4.1.1. But the console version is 5.4.1 (Command: Cordova -version).
I did everything by node.js console.
Attemps:
I uploaded an APK without js components. Only with cordova.js and it not worked.
I installed all over again in a newly installed windows and neither worked.
My version is higher than 3.5.1. I can not find the solution.
The big problem is not just that PLATFORM_VERSION_BUILD_LABEL is wrong, but the default cordova used is ancient ( it was 3.7.1 on mine ). To resolve this you need to install a newer version in the project. You can specify this on the command line, much like npm does.
cordova platform update android#4.1.1
Or you can specify it in your config.xml
<engine name="android" version="4.1.1" />
That may need 'spec' instead of 'version' depending on how current you cordova install is. At this point, they are up to 5.1, and you can use 'latest' instead of a specific version number.
The next headache will be the point of the patch, which locks down network access. I am now getting 404 errors on all my ajax calls to our server. Access was the root of the security problem, so this isn't a big surprise. I am still working on that.
I had the same problem, I found a previous corodva version in a plugin, in my case was facebook connect; I deleted this plugin and upload again, its work form me. You may search PLATFORM_VERSION_BUILD_LABEL in your project, is posible that some plugin have other cordova version.
I was trying to solve this problem almost for a week. Solution:
There was a cordova.js file within www/lib/cordova folder that doesn't get updated when you update cordova and ionic. Open the file and look for var PLATFORM_VERSION_BUILD_LABEL. If the version is not 4.1.1 at the time of this post, update it with another copy of the file that is somewhere in your main directory.