Overriding string resources causes crashes or inelligible strings

[chris6647]

Coming from the Android world, we're used to being able to define a String resource in a feature module, and then have the app override any string keys it may need to. This allows a feature to have defaults, which gets superseeded by the app, as long as they're in the same publicResClass.

Doing so in Compose Resources does not work, due to the offset and size parameters which match the initial StringResource in the feature. When we runtime try to resolve it, it may not match with the final string causing ineligble strings (/empty strings) to be returned, or even crashes if the base64 decoder fails with invalid chars.

Any chance for an implementation that supports this, or ideas for a workaround? So far I havn't been able to come up with anything that I can do from my end of the code. Had a hard time chosing between a bug report or enhancement request - but went with bug due to how the issues surface with wrong texts or crashes.

Similar problem as this issue https://github.com/JetBrains/compose-multiplatform/issues/4837 , but another use case, which will hopefully reconsider :)