Add additional "logging" (via Alert.alert(...)) to provide user with information about potential issues with setting of threadStore/messageStore or with fetchNewCookieFromNativeCredentials. The logic/behavior should be equivalent to before.
Details
Details
NA, careful reading
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Branch
- arcpatch-D5357 (branched from master)
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
native/data/sqlite-context-provider.js | ||
---|---|---|
52 ↗ | (On Diff #17536) | Is this meant to be landed, or just patched in before a release?
|
53 ↗ | (On Diff #17536) | I don't think you can just put an exception inline like this... don't you need to use getMessageForException or something? |
65 ↗ | (On Diff #17536) |
|
native/data/sqlite-context-provider.js | ||
---|---|---|
52 ↗ | (On Diff #17536) | It's meant to be landed, want to minimize the number of temporary "changes before release." I figured it would be fine to provide these alerts even in a general release to help surface any issues, but I'll update so they only apply to __DEV__ or staff. |
53 ↗ | (On Diff #17536) | Here's what I saw locally: I'll modify to use getMessageForException for consistency with rest of the codebase |
65 ↗ | (On Diff #17536) |
|
Comment Actions
address feedback
- limit alerts to __DEV__ or isStaff
- use getMessageForException(...)
- notify user to exit app on fetchNewCookieFromNativeCredentials(...) failure
Comment Actions
Please address feedback before landing
native/data/sqlite-context-provider.js | ||
---|---|---|
81 ↗ | (On Diff #17543) | In the else condition here let's call ExitApp.exitApp() so that the app doesn't hang indefinitely for users |