fix: offline intitalization using cached config #238
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Improve Client Build Process Resilience and Cache Handling
Summary
Enhances the DevCycle iOS Client SDK to gracefully handle network failures during initialization by leveraging cached configurations, while maintaining appropriate error handling for user operations.
Key Changes
🔧 Client Build Process (
setup)👤 User Operations
identifyUser: Uses cached config fallback, only errors if no cache availableresetUser: Always returns errors on network failure (requires fresh anonymous user)🧹 Code Cleanup
Cachestruct andload()method (~50 lines of dead code)🧪 Enhanced Testing
Behavior Matrix
This ensures the SDK works reliably in offline scenarios while maintaining clear error boundaries for operations that require fresh data.