Conversation
|
| App Name | Jetpack | |
| Configuration | Release-Alpha | |
| Build Number | 31039 | |
| Version | PR #25272 | |
| Bundle ID | com.jetpack.alpha | |
| Commit | 694efac | |
| Installation URL | 3plsdnte7o2tg |
|
| App Name | WordPress | |
| Configuration | Release-Alpha | |
| Build Number | 31039 | |
| Version | PR #25272 | |
| Bundle ID | org.wordpress.alpha | |
| Commit | 694efac | |
| Installation URL | 2vke1umln5aa0 |
🤖 Build Failure AnalysisThis build has failures. Claude has analyzed them - check the build annotations for details. |
1a46d04 to
2502056
Compare
| /// It's reserved for Objective-C to Swift interoperability in the context of separating this model from the app target and will be removed at some point. | ||
| @property (nonatomic, strong, nullable) WordPressComRestApi *_private_wordPressComRestApi; | ||
|
|
||
| @property (nonatomic, copy, nullable) NSString *cachedToken; |
There was a problem hiding this comment.
I plan to remove it in the future PR, so it won't be in the public API.
It seems incorrect to cache token on the per-instance basic. The the app cleans the token (account.authToken = nil), in invalidates cachedToken only on this instance. The other instances might continue to return the same invalidated cached token.
In the future PRs, I plan to introduce a shared keychain service that would contain an in-memory dictionary for cached token. It will also allow us to uncomment some of the tests.
2502056 to
5cf03b0
Compare
5cf03b0 to
694efac
Compare
|





This is a first part of the rework of
WPAccountauth token management to Swift. It is more of a mechanical change that doesn't introduce any refactoring.