[SDK] [Cordova] Release HCM v1.0.2
by Olivier FavreThis module adds Huawei Mobile Services HCM support for the WonderPush Cordova SDK v3 on Android.
See our integration guide for more information on how to integrate.
Changelog:
- Initial release
This module adds Huawei Mobile Services HCM support for the WonderPush Cordova SDK v3 on Android.
See our integration guide for more information on how to integrate.
Changelog:
If you use "targetSdk 31" this SDK version isrequired, along with our FCM module v1.0.4 minimum.
For the others, we recommend to always use the latest published version.
Changelog:
targetSdk 31APP_LAUNCH in-app system trigger to match application cold startsIf you use targetSdk 31, this SDK version is required.
You will also need to upgrade the version of our FCM module to v1.0.4 minimum.
Here is a more detailed outline of the changes:
ACTION_CLOSE_SYSTEM_DIALOGS intent.@APP_OPEN events when an activity is resumed after a long time, like Android 12 now does when pressing back on the root activity.If your application uses a custom splash activity, or a routing activtiy to resolve deeplinks using application code, to avoid triggering an in-app shown on app launch or app foreground, you can now mark those activities with the following metadata in your AndroidManifest.xml, inside their <activity> tag:
<meta-data android:name="com.wonderpush.sdk.iam.ignoreForeground" android:value="true" />Note that Android 12 now proposes a convenient API for handling splash screens.
It also adds splash screens automatically to all loading applications, so if you have a custom splash screen activity you should probably migrate your existing splash screen.
Changelog:
This update is required if your application uses targetSdk 31.
This releases fixes the following build error:
Manifest merger failed : Apps targeting Android 12 and higher are required
to specify an explicit value for android:exported when the corresponding
component has an intent filter defined.
Changelog:
Changelog:
If you are facing a Google Play application submission rejection with the cause "Remediation for Implicit PendingIntent Vulnerability", this update is for you.
No customer have currently faced this, considering we were already implementing many best practices, but there was a few more we could take advantage of, which we did in this release.
Changelog:
If your application is submitted to Google Play with the HCM module included, your application may be rejected by the new app release verification rules, mentioning the cause "Remediation for Implicit PendingIntent Vulnerability".
Simply update our HCM module and you should be good to go.
Changelog:
Changelog:
Changelog: