Update: this misdetection was fixed in Pushwoosh Android SDK 6.8.0. If you are seeing non-Huawei devices registered as Huawei, upgrade the SDK — the current release is 6.10.0.
What used to happen
In older SDK versions, if your application's build included the Huawei Mobile Services (HMS) push dependency, the SDK checked HMS availability to decide the device platform. On some non-Huawei Android devices that shipped HMS Core, this check could produce a false positive and the device was registered as a Huawei device.
Current behaviour
The SDK now uses a three-level check before selecting HMS Push:
- The device's
Build.MANUFACTURERorBuild.BRANDmust contain "huawei" or "honor". - HMS Core must be installed and available.
- Google Play Services must not be available — if a device has both GMS and HMS, GMS wins.
As a result, Xiaomi, OnePlus, Google Pixel and other non-Huawei devices are no longer registered as Huawei even when the HMS dependency is present in the build.
What to do
- Upgrade the Pushwoosh Android SDK to 6.8.0 or later (6.10.0 is current). This alone resolves the misdetection.
- Re-open the app on an affected device so it re-registers with the correct platform. Existing wrongly-typed device records will be replaced on the next registration.
- Separate build flavours for Google Play and Huawei AppGallery are still a reasonable practice for keeping APK size down and avoiding unnecessary HMS dependencies, but they are no longer required to get correct platform detection.
Comments
0 comments
Please sign in to leave a comment.