Initialization Issues
SDK Not Initialized
SDK Not Initialized
Error:
Stringboot SDK is not initializedSolution: Ensure you have configured the AndroidManifest.xml correctly or called StringProvider.initialize() in your Application.onCreate().Invalid API Token
Invalid API Token
Error:
401 UnauthorizedSolution: Double-check your API token in the dashboard. Ensure you are using the correct token for the environment (Dev vs Prod).String Issues
Strings showing as ??key??
Strings showing as ??key??
Cause: The string key was not found in the local cache.Solutions:
- Ensure the key exists in the dashboard.
- Ensure you have run
StringProvider.refreshFromNetwork()at least once. - Check if the device is offline and the cache is empty.
UI Not Updating
UI Not Updating
Cause: XML views do not automatically update when the locale changes.Solution: Call
binding.root.applyStringbootTags() after changing the locale or receiving a sync update.Build Issues
Duplicate Class Definition
Duplicate Class Definition
Cause: Conflict with another library using similar dependencies (e.g., Room, Retrofit).Solution: Check your dependency tree and exclude conflicting transitive dependencies if necessary.