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
iOS has an ongoing issue affecting 1-2% of users, which we think could be the same crash. This is a good starting point so for now, I'll attach it to this issue.
Looking at the crash description: [__NSSingleObjectArrayI stringValue]: unrecognized selector sent to instance 0x3018683b0, it comes from trying to call stringValue on an NSArray which does not implement this method. It seems that NSArray was never properly handled so we just return early in such cases: https://github.com/Expensify/Mobile-Expensify/pull/13413
Activity
Julesssss commentedon Feb 3, 2025
iOS has an ongoing issue affecting 1-2% of users, which we think could be the same crash. This is a good starting point so for now, I'll attach it to this issue.
iOS logs show that it occurs in YAPLLogManager.getSecureParamString.
This might be a good task for our SWM external teams, I'll speak with Mariusz today and see if anyone in the team can take a look.
Julesssss commentedon Feb 5, 2025
@WoLewicki some additional logs:
logs1.log
stacktrace1.txt
WoLewicki commentedon Feb 5, 2025
Looking at the crash description:
[__NSSingleObjectArrayI stringValue]: unrecognized selector sent to instance 0x3018683b0, it comes from trying to callstringValueon anNSArraywhich does not implement this method. It seems thatNSArraywas never properly handled so we just return early in such cases: https://github.com/Expensify/Mobile-Expensify/pull/13413