In-App Update API showing UPDATE_NOT_AVAILABLE while testing on debugging device

When Internal app sharing dont work
-----------------------------------

Internal App Sharing is not working on a real device. I was testing several hours and always got the latest version of **Internal Test** and not the one of **Interal App Sharing** that was what I expected.

# The solution is to use an emulator with Play Store.


*I describe the step by step:*

1. **Create Virtual Device with Google Play** greater than or equal to API Level 21 5.0.
2. Open the emulator and log in with the google account that is in the list of internal testers.
3. Build the 2 APKs with different versions. Each one with the same **versionCode and versionName temporarily** to go checking when performing the installations. For example:

____

APK 1: versionCode and versionName: 100

APK 2: versionCode and versionName: 101

____

4. Upload APK 1 to [internalappsharing][1] with versionCode and versionName 100

5. Copy and paste the shared link of APK 1 into [Keep Notes][2] web app.
6. Install APK 1 with versionCode 100 using the link from the emulator Keep Notes application.
7. The most important thing: **Check that the installed app has versionName 100.**
8. If we open APK 1 at this point, no update will be available until we upload APK 2 with a larger version.
9. Upload APK 2 with code 101 to [internalappsharing][1]
10. Copy and paste the APK 2 link into Keep Notes web app.
11. DO NOT install APK 2 from the link. Just enter APK 2 link to check that the Play Store describes the existence of an update.
12. Open the app installed on the emulator with APK 1 and install the update in-app.

Finally, each time they enter a link with a version code greater than the last installed from the emulator they will see the existence of a new update, which should be installed within the app and not from the Play Store.

[![enter image description here][3]][3]

___

It is worth mentioning that **Logcat** is compatible with Internal App Sharing.

GL

[Source][4]


[1]:

[To see links please register here]

[2]:

[To see links please register here]

[3]:

[4]:

[To see links please register here]

As of today, in-app-update testing can not be done for a debug build. You don't need to put your apk to PlayStore to test also. The best way to test `in-app-update` is by using `internal-app-sharing`.

If you follow the below steps one-by-one, you'll be able to test successfully.

1. To test the app, a tester has to first enable Internal-App-Sharing in PlayStore, follow this link for the same,

[To see links please register here]

2. If you're brave enough to understand the official documents, then simply follow this link to set-up `in-app-update` testing in your device,

[To see links please register here]

Here, I'll be writing the same in easy words.

Once you're done with setting up `internal-app-sharing` in `Play-Store`, make sure that you have to upload 2 apks to internal-app-sharing on `Play-Console` and hence generate 2 links. Both apks will be signed using the same `signing-key` (need not be the same as the one you use to sign for production, any dummy signing-key would work).

3. First you upload an apk with in-app-update implementation with lower VersionCode (say, 100) to internal-app-sharing on play console.

To know, How to upload apk to internal-app-sharing on Play-Console, follow this lisk,

[To see links please register here]

**NOTE**: make sure, you have uninstalled any preinstalled app with the same package-name in your device.

4. Now you copy the link of the app you uploaded to internal-app-sharing on the play console and use this link to install the app on your device.

NOTE: Before installing, make sure the email-id you're using on play-store has been added in the mail-list on internal-app-sharing on play-console.

5. Now, once you've installed the app using the link. Now, you need to again create a new signed apk with higher VersionCode (say, 101). And upload this apk to internal-app-sharing.

6. Now, copy the link with higher VersionCode from internal-app-sharing. Click on this link on your device, it will take you to play-store but this time, `update` button will be enabled rather than `install` button as app is already installed in your device with lower VersionCode.

7. You don't have to click the update button on PlayStore. You just have to click the link and hence open the screen on PlayStore. Now close PlayStore app.

8. Now, you can launch the already installed app from your device.

If your implementation of in-app-update is fine, launching the app would appear the dialog from PlayStore for update.

> Lastly, don't forget to upvote if it helps you in any way. Keep
> Coding!

I struggled with this same problem for a few days before once again going through the documentation thoroughly. Read [this section][1] on the official documentation of the in-app updates.

The link describes the correct testing procedure as follows:

> 1. On your test device, make sure you've already installed a version of your app that meets the following requirements:
- The app was installed using an internal app sharing URL
- Supports in-app updates
- Uses a version code that's lower than the updated version of your app

> 2. Follow the Play Console instructions on how to share your app internally. Make sure you upload a version of your app that uses a version code that's higher than the one you have already installed on the test device.
> 3. On the test device, only click the internal app-sharing link for the updated version of your app. Do not install the app from the Google Play Store page you see after clicking the link.
> 4. Open the app from the device's app drawer or home screen. The update should now be available to your app, and you can test your implementation of in-app updates.

This is also super helpful because you don't have to wait for the app to be published, you can start testing immediately.

[1]:

[To see links please register here]