Hello sunbae, I can't get the hang of it at all, so I'm posting a question here.
The current situation is that the existing Google Play Store app was registered Due to the large-scale patch, we updated it to a completely different app from the existing one. (The package name is the same, but the source code itself is wrong)
The update to the Google Store has been successfully completed, StartActivity registered as launcher registered in manifest does not work The phenomenon of entering HomeActivity immediately occurred.
/<activity
android:name=".StartActivity"
android:screenOrientation="portrait"
android:theme="@style/AppTheme.NoActionBar.Yellow">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity
android:name=".HomeActivity"
android:screenOrientation="portrait"
android:launchMode="singleTask"/>/
If you delete the app and install it again, you will get the proper start activity registered as launcher I would like to ask you the reason why the upgrade terminal does not take StartActivity registered as launcher.
I don't know if there was a lack of explanation, but if there is anyone who knows, please let me know in the reply.
main launcher
This appears to be caused by the launcher shortcut icon's information notification icon. When the launcher creates a shortcut icon, it constructs its own database based on ComponentName (package name + activity name), and it is assumed that this information remains as an existing HomeActivity rather than StartActivity.
Usually, if the entry activity changes, the launcher should handle it, but there are no guidelines for this part, so each launcher has a different approach. If you want to check if it's a launcher problem, click on the icon in the app drawer (list) to run it, not the existing desktop icon. If it works well, it is correct that the launcher does not properly update the shortcut information on the desktop. In this case, I think one of the ways is to guide the user to install a new shortcut icon. (Delete existing shortcut icons)
In fact, it's not common for entry activity to change, but you can use activity-alias in case of this.
However, in the current case, it seems difficult to follow up with the above method because an update that modified the entry activity has already been distributed. If you think something similar will happen in the future, try using activity-alias.
© 2024 OneMinuteCode. All rights reserved.