07-20-2023, 04:29 PM
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]:
[4]:
-----------------------------------
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]