[Fixed] Error 502 when calling an API in AMAPI
Update: as of 2nd April 2025 01:37 PM GMT Issue description: We have received multiple reports that AMAPI endpoints are receiving Error 502. The issue appears to be intermittent. Current status: [Fixed] Our Engineering Team has confirmed that the issue is now fixed. If you were previously experiencing this issue, please can you check if this is now working as expected. Thank you for time and patience. Android Enterprise Customer Community Team[Fixed] MGP iFrame is returning 501 error
Update as of 2/21 10:07 PM GMT Status: [Fixed] Search Play store tab in iframe is now fixed. It should display the correct page instead of the Organize Apps. Update as of 11:30 AM GMT, 21st February 2025 Status: [Fixed] 501 Error in iFrame The issue regarding accessing Managed Google Play iFrame returns 501 error is now fixed. Please do continue to let us know how this is working for you. Many thanks for your help. Android Enterprise Customer Community Team[Action needed] New Android zero-touch customer portal launched!
We're excited to announce that our new, improved zero-touch customer portal is now live! It was released in early June (as an opt-in) with a refreshed user interface and enhanced functionality, making it easier and more efficient for you to manage your zero-touch devices. Migration Timeline: Starting next month (July 2024), we'll begin migrating all customers to the new portal. Once migrated, the old portal will not be accessible. Action Required: Explore the New Portal: To familiarize yourself with the new portal, simply click the new tab that is visible in your current customer portal or can follow this link. Update Links: Please save the new portal link below and update any internal documentation referencing the old portal: New Customer Portal Link: https://enterprise.google.com/android/zero-touch/customers/ Important Note: The zero-touch customer API will remain unaffected by this change. We're confident that you'll find the new portal a significant improvement over the old one. Please refer to this article for more information. If you have any questions about this announcement, post them in the general discussion board. Lastly, we'd like to say a special thanks to those customers here in the Customer Community who took part in the early access program and for the feedback your provided.[FIX Available] TosError responses accessing zero-touch customer API
24th May, 2024 We have recently updated the zero-touch customer terms of service and customers will be prompted to accept the terms of service upon next login to the zero-touch customer portal. Issue: This may cause an increase in TosError responses (https://developers.google.com/zero-touch/reference/customer/rest/v1/TosError) when attempting to access the zero-touch customer API. Any existing solutions leveraging the zero-touch customer APIs to access an account that has not yet accepted the new terms of service will receive a TosError response. Resolution: Customers will need to accept the terms of service by signing in to the zero-touch enrollment portal. If you are currently experiencing this issue or have any questions or concerns, please add your comments to the existing conversation here. Massive thanks to those community members who reported this here.[FIXED] Some Fully Managed devices unable to update Play Store version
Updated: February 22nd, 2024 Issue: Some Fully Managed devices running Android 11 and below have received a version of the Play Store that cannot self-update to the newest versions. Work Profile devices, including both personally and company-owned devices, are not impacted. Affected devices can still install and update other applications as normal. This issue can be verified on the device, by long pressing the Play Store icon and tapping the info icon. Impacted devices will have the Play Store version 35.2.19 or below. Bugreports from these devices may also show entries as follows when attempting to update. “PackageManager: Package com.android.vending signatures do not match previously installed version; ignoring!” Current status: A fix has been applied to prevent additional Fully Managed devices getting into this state. A recovery version of the Play Store has been developed that will correctly install on the affected devices. This is a minimal version that has one purpose: to immediately self-update to the correct, regular version of the Play Store. This recovery version of the Play Store began rollout on Dec 8, 2023 and is now complete. Not all devices could be recovered in this way. Note that if a device has DISALLOW_UNINSTALL_APPS restriction set then the recovery service will not be able to complete. The device will show an app named "Play Store Recovery Service" in place of the Play Store and the version code of com.android.vending will be 83540000. Remove this restriction from any such devices for 24 hours and the recovery service will complete successfully. Workarounds: On some devices, users can manually resolve the problem for their device by following these steps: Long press the Play Store icon on the home screen. Choose “App Info” Tap the three dots in the top right corner Uninstall Updates -> Ok Open the Play Store -> Menu Icon -> Settings -> Play Store version Click Update Play Store Message “A new version will be installed shortly” 7. Close Play. A successful update should occur within the next few hours. If DISALLOW_APPS_CONTROL or DISALLOW_UNINSTALL_APPS are set then the user will not be able to apply this manual workaround. Previous update:
