Forum Discussion
Application report not getting collected on Xiaomi mix fold devices
We have couple of users who have the Xiaomi Fold device and in the application report section of status report notifications we are only getting the android device policy app. None of the other applications are getting returned. Is this a known issue? How can we debug the issue? I was not able to see anything obvious in the device logs.
We are getting the full application report for the other devices.
14 Replies
Hey Prathik,
Thanks for the update here.
I've just had a quick look at the ticket and the good news is it appears our engineering team have looked into it and responded to your partner. I would recommend getting back in touch with your Xiaomi contact to work out the next steps with this, based on your current setup.
I hope that helps and fingers crossed you can get this sorted.
Thanks,
Lizzie
Update: Xiaomi has cut a partner ticket for the issue
https://partnerissuetracker.corp.google.com/issues/445867546.
Emilie_B Lizzie Can you please help prioritize this. Thank you.Thanks for the suggestion. We are currently not in the partner portal. We were able to get someone from Xiaomi to look into the logs and they root caused the issue to be a crash in the ADP app which was then failing to fetch application list. The below was their response.
Hi Developer,
We have analyzed the crash logs you provided for com.google.android.apps.work.clouddpc launching com.amazon.enterprise.access.android.
From the stack trace, the root cause is clear:
android.util.AndroidRuntimeException: FORWARD_RESULT_FLAG used while also requesting a result
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2476)
This happens when an activity uses Intent.FLAG_ACTIVITY_FORWARD_RESULT while also calling startActivityForResult(). These two mechanisms are mutually exclusive:
FLAG_ACTIVITY_FORWARD_RESULT indicates that the current activity will forward the result to its caller.
startActivityForResult() indicates that the current activity itself expects to receive a result.
Since the logic conflicts, the framework throws an exception during checkStartActivityResult().
Additionally, we have confirmed that there are no permission restrictions on our system side that would block this behavior.
Lizzie Emilie_B what would be the best way to get the ADP team on this issue?
Thank you for the support.Hi Prathik - Happy Wednesday!
I've heard back from the team and they've said the following:
Based on the crash log from Xiaomi, this appears to be a bug within Google's Android Device Policy app (com.google.android.apps.work.clouddpc), not a simple configuration issue.
Unfortunately, we can't provide such advanced support through the community.
So, the official process for a bug of this nature would be for the OEM (Xiaomi) to contact Google directly through their established partner channels.
Xiaomi's engineering team needs to work with Google to resolve this issue in the core app.
I hope this helpful and provides more context :)
Emilie
To add to the above comment, there are devices that have been AER validated for Android 15 (HyperOS 2 for Xiaomi devices) but is still running into this issue. For example https://androidenterprisepartners.withgoogle.com/device/#!/aRavhC5kIcMYHnc6caO6.
This should be picked up by Google. It's ADP failing to fetch the application list. AMAPI is not limited strictly to supporting AER devices and clearly there's a 6-month issue with the app going unfixed.
Prathik this could also go in via PED, if you or the vendor you use is in the partner portal. A few but reports and raising it as a ADP bug there may help.
Hi Emilie,
We are still getting customers report regarding this issue. One commonality we have observed is that all the devices use HyperOS. We have gotten any support from Xiaomi unfortunately.
Hi Lizzie,
Thanks for reply and we couldn't get any reply from OEMs. Our employees are impacted using these devices. Do you have any recommendations or channel with OEMs ?
Hi sarathm and welcome to the community!
I’m sorry to hear that you could not get any reply from your OEM.
It might be worth contacting Xiaomi OEM if possible - Xiaomi would know if these are the only logs intended to be collected by its devices and, if there are any discrepancies, Xiaomi can report it to Google and work alongside support in determining the issue.
Prathik do you have an update on what happened your end?
Hey Prathik,
Great to see you back in the community - how are you? I hope you are doing well.
Thanks for highlighting this. Have you contact your OEM directly about these devices, they might be able to help work out what is happening here. Is this happening on any other devices? And has this problem always been like this or has this issue just started?
As a side note, checking in the Android Enterprise Solutions Directory this specific device doesn't look it's gone through AER (Android Enterprise Recommended) validation yet - this might also be helpful for your OEM to submit this device to go through this process.
Hope this is a useful starting point. Speak to you soon.
Thanks,
Lizzie
