Closed pa-chihaya-katagi closed 3 years ago
Hi @pa-chihaya-katagi, thanks for your report! Currently, the MAM SDK does not require android.permission.READ_PHONE_STATE
or invoke TelephonyManager.getCallState()
and should not impact usages of it. It appears that your app or another non-MAM dependency invokes this method.
Based on the [Android docs for TelephonyManager.getCallState()
](https://developer.android.com/reference/android/telephony/TelephonyManager#getCallState()), your observation is the expected behavior. The READ_PHONE_STATE permission is now required for applications targeting API level 31+.
@codylund Thank you! I understand now. I did not do enough research. I'm sorry. I will check the product code again.
Thanks for confirming, @pa-chihaya-katagi! Closing this issue, because we believe the behavior is expected. Feel free to reopen if you discover otherwise.
Describe the bug: When I do a fresh install of the app and launch the app, it crashes.
Exception is thrown because phone permissions are not allowed. If I allow phone permissions before launching the app, it will not crash.
To Reproduce
Steps to reproduce the behavior:
Expected behavior: App should not crash.
Screenshots and logs:
Smartphone (please complete the following information):
Intune App SDK for Android (please complete the following information):