Bitmoji Custom Keyboard (null) after Upgrade
| Originator: | rudolf | ||
| Number: | rdar://28363599 | Date Originated: | 19-Sep-2016 |
| Status: | Open | Resolved: | |
| Product: | iOS | Product Version: | |
| Classification: | Custom Keyboard Extension | Reproducible: | Sometimes |
When the Bitmoji app is updated to a new version, some users see our keyboard as (null) - Bitmoji when trying to switch to the Bitmoji custom keyboard. The keyboard is no longer accessible. The users would have to delete the keyboard and re-add it in order to access the keyboard again. It's not certain if the Bitmoji keyboard was the active keyboard before the app is updated.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!
It appears from the logs that when the Bitmoji app is updated, the keyboard extension has a new pid. My speculation is if the Bitmoji keyboard is an active keyboard for a particular app when the Bitmoji app is updated, that app holds on to the now old keyboard process, which is detached from the Bitmoji app. Hence it shows "(null) - Bitmoji Keyboard" in the custom keyboard list