You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my already deployed app, I've got an error feedback which is that my app can not read the message. I've checked every log and observed the situation on user's phone.
The problem is intead of the actual code in the message the OS sends back the B002 part of the message as the code. Furthermore my regex checks not accepting this code and user can not use this function. (This function is mandatory in this app so user can not use the app itself !)
My conclusion is the OS is not recognizing the REGEX given to the SmsAutoFill. And returning the last word in the message. Here is a part of my code:
There is no problems on any other Android device. I got this error only on one user's device which has OS as Huawei HMS. Downloaded app via GBox trough Google Play (This might be the one causing problem too).
Anyone else got this problem? Or as temporary solution, Is there a way to get the whole the message then parse the code myself ?
The text was updated successfully, but these errors were encountered:
On my already deployed app, I've got an error feedback which is that my app can not read the message. I've checked every log and observed the situation on user's phone.
The problem is intead of the actual code in the message the OS sends back the
B002
part of the message as the code. Furthermore my regex checks not accepting this code and user can not use this function. (This function is mandatory in this app so user can not use the app itself !)My conclusion is the OS is not recognizing the REGEX given to the SmsAutoFill. And returning the last word in the message. Here is a part of my code:
There is no problems on any other Android device. I got this error only on one user's device which has OS as Huawei HMS. Downloaded app via GBox trough Google Play (This might be the one causing problem too).
Anyone else got this problem? Or as temporary solution, Is there a way to get the whole the message then parse the code myself ?
The text was updated successfully, but these errors were encountered: