# Android EMM Known Issues

### Functionality

<table id="bkmrk-%C2%A0-%C2%A0-%C2%A0-issue-notes-re" style="width: 107.284%; height: 591.118px;"><thead><tr style="height: 29.7969px;"><td style="width: 56.9726%; height: 29.7969px;">Issue</td><td style="width: 30.5125%; height: 29.7969px;">Notes</td><td style="width: 12.5149%; height: 29.7969px;">Reference</td></tr></thead><tbody><tr style="height: 29.7969px;"><td style="width: 56.9726%; height: 29.7969px;">Enrollment of more than 500 devices is blocked by Google's API</td><td style="width: 30.5125%; height: 29.7969px;">[https://bayton.org/blog/2024/03/amapi-permissible-usage/](https://bayton.org/blog/2024/03/amapi-permissible-usage/) discusses this issue introduced in Q4/2024 by Google. The AMAPI API has a hard limit now of 500 devices by default. There is a form: [https://goo.gle/android-enterprise-response](https://goo.gle/android-enterprise-response) that can request that Google raise this limit for your account.</td><td style="width: 12.5149%; height: 29.7969px;"> </td></tr><tr style="height: 29.7969px;"><td style="width: 56.9726%;">Can not import or create placeholders</td><td style="width: 30.5125%;">FileWave hopes to implement in future release</td><td style="width: 12.5149%; height: 29.7969px;">  
</td></tr><tr style="height: 29.7969px;"><td style="width: 56.9726%; height: 29.7969px;">Devices do not show in smart groups</td><td style="width: 30.5125%; height: 29.7969px;"> </td><td style="width: 12.5149%; height: 29.7969px;"> </td></tr><tr style="height: 46.5938px;"><td style="width: 56.9726%; height: 46.5938px;">No paid app distribution (AKA group license purchases)</td><td style="width: 30.5125%; height: 46.5938px;">Paid apps not currently implemented in Google API</td><td style="width: 12.5149%; height: 46.5938px;"> </td></tr><tr style="height: 46.5938px;"><td style="width: 56.9726%; height: 46.5938px;">Wiping device, but not removing from FW does not get previous associations</td><td style="width: 30.5125%; height: 46.5938px;">FileWave hopes to implement in future release</td><td style="width: 12.5149%; height: 46.5938px;">GOOG-216</td></tr><tr style="height: 225.766px;"><td style="width: 56.9726%; height: 225.766px;">Compliance policy breaks model update  
  
**Error at model update:**  
  
```sql
[ERROR] 2019-06-07 15:50:56,075 (exception): Internal Server Error: /android/emm/process_pending_emm_calls/<br>Traceback (most recent call last):[...]googleapiclient.errors.HttpError: <HttpError 400 when requesting https://androidmanagement.googleapis.com/v1/enterprises/LC01d4gn82/policies/default?alt=json returned "complianceRules are deprecated. Use policyEnforcementRules instead."
```

</td><td style="width: 30.5125%; height: 225.766px;">Google API was suddenly changed.  
  
Code fix already in future release.  
  
If you were on 13.1.0 when EMM was enabled in your license, then you will need a fix before or after upgrading to 13.1.1.  
  
To request a patch use the [Feedback Portal : Question](https://jira.filewave.com/servicedesk/customer/portal/8/create/60) (must be apart of the EMM program to use)</td><td style="width: 12.5149%; height: 225.766px;"> </td></tr><tr style="height: 152.977px;"><td class="align-left" style="width: 56.9726%; height: 152.977px;">Default Apps removed after enrolment</td><td style="width: 30.5125%; height: 152.977px;">Google standard behaviour is to remove default, installed apps on enrolment.

[Workaround available in 15.3+](https://kb.filewave.com/books/android/page/android-system-apps)

GUI option to follow in a future update.

</td><td style="width: 12.5149%; height: 152.977px;">GOOG-965</td></tr></tbody></table>

### Minor (Aesthetics) Issues

<table id="bkmrk-%C2%A0-%C2%A0-%C2%A0-issue-notes-re-1" style="width: 100%;"><thead><tr><th style="width: 33.8688%;"> </th><th style="width: 52.7814%;"> </th><th style="width: 13.3498%;"> </th></tr></thead><tbody><tr><td style="width: 33.8688%;">Issue</td><td style="width: 52.7814%;">Notes</td><td style="width: 13.3498%;">Reference</td></tr><tr><td style="width: 33.8688%;">You cannot put the FileWave Client APK on an EMM enrolled device</td><td style="width: 52.7814%;"> </td><td style="width: 13.3498%;"> </td></tr><tr><td style="width: 33.8688%;">Closing and reopening the Android signup window before completion will display the wrong Google Org Name</td><td style="width: 52.7814%;">FileWave hopes to implement in future release</td><td style="width: 13.3498%;">GOOG-187</td></tr><tr><td style="width: 33.8688%;">No Command History in device details</td><td style="width: 52.7814%;">FileWave hopes to implement in future release</td><td style="width: 13.3498%;">  
</td></tr><tr><td style="width: 33.8688%;">The Serial Number I see in FileWave does not match the Serial Number I see on the device.</td><td style="width: 52.7814%;">Some devices (Predominately Samsung) have two serial numbers, to see these on the device: Settings &gt; Google &gt; Device Policy &gt; ⋮ (vertical ellipse) &gt; Device Details. Scroll to the bottom to see the serials.</td><td style="width: 13.3498%;"> </td></tr></tbody></table>