sp-react-native-in-app-updates icon indicating copy to clipboard operation
sp-react-native-in-app-updates copied to clipboard

Installation always giving error status:5

Open Lekhrajk opened this issue 2 years ago • 5 comments

This is what i am getting everytime during installation

download status {"bytesDownloaded": 0, "status": 11, "totalBytesToDownload": 0}
 download status {"bytesDownloaded": 0, "status": 3, "totalBytesToDownload": 0}
 download status {"bytesDownloaded": 0, "status": 5, "totalBytesToDownload": 0}

Please look into this

Device : Realme1, OS Type : Android 9, Package version : sp-react-native-in-app-updates: "^1.1.7",

Lekhrajk avatar Jun 18 '22 13:06 Lekhrajk

same here

rvuyyuru1 avatar Aug 02 '22 09:08 rvuyyuru1

@Lekhrajk @rvuyyuru1 did you manage to solve this issue?

ddikodroid avatar Sep 16 '22 08:09 ddikodroid

no

rvuyyuru1 avatar Sep 21 '22 11:09 rvuyyuru1

If anybody else faces this issue, check that the version the application tries to update to has a matching signature with the updating app.

My issue was that the test app tried to update to a production version in Playstore, which used a Google generated signature. This caused the signatures to not match, and the PackageManager ignored the application, and the installation failed.

taneli1 avatar Oct 15 '22 15:10 taneli1

If anybody else faces this issue, check that the version the application tries to update to has a matching signature with the updating app.

My issue was that the test app tried to update to a production version in Playstore, which used a Google generated signature. This caused the signatures to not match, and the PackageManager ignored the application, and the installation failed.

This is correct. I just explain more about the way you can test your app. Clearly that you can not just react-native run-android and react-native start to run the local test app like normal. Moreover, you can not build the apk with your custom keystore (custom signingConfigs) which you used to build the abb file and uploaded it to chplay. Because when you upload abb to play.google.com, google signs your abb file with another keystore. So you still get status 5 in the apk that you build.

The solution that using the internal testing in the google play console with the same account that you use to deploy your app. image

You may know how to use it. This is the way that I do for someone who doesn't familiar. Generate the abb with a lower version code in the android>app>build.grapdle>versionCode (example: 1) for the internal testing and install it manually on your phone. After changing something in your app to see the difference and increase the version code (example: 2) then upload it to the internal testing. You may need to wait a few minutes.

ngotra2710 avatar Feb 22 '23 16:02 ngotra2710