Closed yhirano closed 1 year ago
I'm Nagai of Star Marketing Japan. Thank you to give us this issue. I understood your problem, but unfotunatery I have no answer. Bandit, Please give us your advice.
We received the information from Star Micronics. Star Micronics plans to support this in the next Ver. The timing is undecided. Thanks, Nagai.
There may be a problem with the obfuscation settings.
I'm guessing that setting -keeppackagenames
to Proguard/R8 may solve this problem.
The following may be helpful for you. https://stackoverflow.com/questions/67492135/how-can-i-obfuscate-the-package-names-for-two-different-aar-without-having-du
Thank you for providing useful information. We will use it as a reference for the next Ver.
@yhirano Star Micronics fixed this problem on Star Xpand SDK for ReactNative Ver.1.2.0. This SDK is already available. The official comment from Star Micronics is as below. Thanks.
[Android]
@yhirano i'm going to close this issue since it has been fixed. we'd love to get your feedback if you have any.
When building our app for Android using react-native-star-io10, the following error occurred. This error seems to occur because react-native-star-io10 and other libraries have conflicting obfuscated class names.
To fix this problem, can you change interface names in stario10.aar to globally unique interface names, or hide interfaces obfuscated interfaces like
a.a.a.a
? I cannot fix this problem myself because stario10.aar is a closed library.