Android Custom Client APK Version Code Is Always 58

May 14, 2025 by ADMIN 52 views

Android Custom Client APK Version Code Always 58: A Critical Issue in Google Play Updates

Bug Description

When building an Android custom client using the RustDesk Pro environment, the resultant APK file consistently uses a Version Code of 58. This issue arises from the fact that the version code is derived from the pubspec.yaml file, which is in the format A.B.C+XX, where A.B.C becomes the versionName, and XX becomes the versionCode. In the current release build, the pubspec.yaml version is 1.4.0+58, resulting in APKs with a fixed version code of 58.

This problem poses a significant challenge when attempting to update a private Android app in Google Play. Since the version code remains the same, Google Play rejects the updated APK, citing that it is identical to the currently published version. This issue highlights the importance of ensuring that the version code is incremented correctly to facilitate seamless updates.

How to Reproduce the Issue

To replicate this issue, follow these steps:

Install Android Studio or Android SDK Platform Tools: Begin by installing either Android Studio or the Android SDK Platform Tools on your system.
Create and Build an Android Custom Client: Create an Android custom client using your RustDesk Pro environment, utilizing any package name you prefer.
Install the Custom Client: Install the custom client on an Android device or an Android Studio emulated device.
Enable Developer Options: Enable developer options on the device by navigating to Settings > About Phone > tap Build Number 7 times.
Enable USB Debugging: Ensure that USB Debugging is enabled by navigating to Settings > System > Advanced > Developer Options > USB debugging.
Connect the Device to Your PC: Connect your device to your PC (if using a physical device) or use an emulated device in Android Studio.
Retrieve the Version Code: Use the adb command to retrieve the version code from your APK:
- For Linux: adb shell pm dump com.app.packagename | grep versionCode
- For Windows: adb shell pm dump com.app.packagename | FIND /I "versionCode"
Modify the Android Custom Client: Modify your Android custom client in some way, ensuring that the app name and package name remain unchanged.
Save and Rebuild the App: Save and rebuild the app to generate a new APK.
Install the New Version: Install the new version of the app and run the same adb commands to retrieve the version code.
Compare the Version Codes: Compare the version codes of the original and new APKs to verify that the issue persists.

Expected Behavior

The resulting version code returned by the adb command should be incremented by at least 1 in the new version of the app. This indicates that the version code has been updated correctly, allowing for seamless updates in Google Play.

Operating System and RustDesk Version

The issue is observed on the following configurations:

Local (Controlling) Side: Linux (RustDesk Server)
Remote (Controlled) Side: Android
RustDesk Version: 1.4.0

Screenshots

Image 1 Image 2 Image 3

Additional Context

To resolve this issue, it is essential to ensure that the version code is incremented correctly. One possible solution is to introduce a manual version number within the custom client configuration, allowing users to manually increment the version code as necessary. This approach would enable users to update their apps without relying on automated version code updates.

However, if an automated solution is preferred, it is crucial to consider the starting point of the version code. In this case, starting from 1 and incrementing by 1 for each update would require editing the app 58 times before reaching a usable version for the already deployed app. This highlights the importance of carefully designing the version code update mechanism to ensure seamless updates in Google Play.

By understanding the root cause of this issue and implementing a suitable solution, developers can ensure that their Android custom clients are updated correctly, facilitating a smoother user experience and reducing the risk of app updates being rejected by Google Play.
Android Custom Client APK Version Code Always 58: A Q&A Article

Q: What is the root cause of the issue where the Android custom client APK version code is always 58?

A: The root cause of this issue is that the version code is derived from the pubspec.yaml file, which is in the format A.B.C+XX, where A.B.C becomes the versionName, and XX becomes the versionCode. In the current release build, the pubspec.yaml version is 1.4.0+58, resulting in APKs with a fixed version code of 58.

Q: Why is this issue a problem for updating private Android apps in Google Play?

A: This issue is a problem because Google Play rejects updated APKs with the same version code as the currently published version. Since the version code remains the same, updates are not allowed, and users cannot access the latest features and improvements.

Q: How can I reproduce this issue?

A: To reproduce this issue, follow these steps:

Install Android Studio or Android SDK Platform Tools.
Create and build an Android custom client using your RustDesk Pro environment.
Install the custom client on an Android device or an Android Studio emulated device.
Enable developer options and USB debugging on the device.
Use the adb command to retrieve the version code from your APK.
Modify the Android custom client in some way and rebuild the app.
Install the new version of the app and run the same adb commands to retrieve the version code.
Compare the version codes of the original and new APKs to verify that the issue persists.

Q: What is the expected behavior for the version code?

A: The expected behavior for the version code is that it should be incremented by at least 1 in the new version of the app. This indicates that the version code has been updated correctly, allowing for seamless updates in Google Play.

Q: What are the operating system and RustDesk version configurations where this issue is observed?

A: The issue is observed on the following configurations:

Local (Controlling) Side: Linux (RustDesk Server)
Remote (Controlled) Side: Android
RustDesk Version: 1.4.0

Q: What are the possible solutions to this issue?

A: Two possible solutions to this issue are:

Manual version number: Introduce a manual version number within the custom client configuration, allowing users to manually increment the version code as necessary.
Automated version code update: Implement an automated solution to update the version code, ensuring that it is incremented correctly for each update.

Q: What are the considerations for implementing an automated version code update solution?

A: When implementing an automated version code update solution, consider the following:

Starting point: Ensure that the starting point of the version code is not too low, as this may require editing the app multiple times before reaching a usable version for the already deployed app.
Incrementation: Decide on the incrementation method, such as incrementing by 1 for each update or using a more complex algorithm.

Q: How can I ensure that my Android custom clients are updated correctly?

A: To ensure that your Android custom clients are updated correctly, follow these best practices:

Use a manual version number: Consider introducing a manual version number within the custom client configuration to allow users to manually increment the version code as necessary.

Implement an automated version code update solution: If you prefer an automated solution, ensure that it is designed to increment the version code correctly for each update.
Test thoroughly: Thoroughly test your app updates to ensure that they are working correctly and that the version code is updated correctly.