[rive-native] print duplicates error

[kimtami]

if using soloud and rive-native packages.
this warning appear to console window.

objc[18661]: Class ma_ios_notification_handler is implemented in both 
/private/var/containers/Bundle/Application/6530BDFE-7889-4C39-A90F-
003132CEBF18/Runner.app/Frameworks/rive_native.framework/rive_native (0x106620f40) and 
/private/var/containers/Bundle/Application/6530BDFE-7889-4C39-A90F-
003132CEBF18/Runner.app/Frameworks/flutter_soloud.framework/flutter_soloud (0x1053046f8).
This may cause spurious casting failures and mysterious crashes. One of the duplicates must be removed or renamed.

and this issue raised rive animation init crash.

and found init crash issue solution:

1. remove soloud(or duplicates package)
2. flutter clean & flutter pub get
3. flutter run

[HayesGordon]

@kimtami I just want to make sure I understand. Are you just getting a warning, or are you failing to compile the app? Which platform is giving this error?

[kimtami]

Discovery Process

The issue was discovered through the following steps:
• Some graphic components were not visible, but this phenomenon only occurred in the iOS simulator
• No issues were observed on actual devices
• Initially suspected it was a cache problem, so we reset the project dependencies almost completely, but the issue persisted
• After noticing the warning message in Xcode and removing the duplicate library, rendering returned to normal
Conclusion: This was not just a warning-level error - it had actual functional impact.

[HayesGordon]

@kimtami thanks for the info. So this is only reproducing on a simulator, but it is working on a real device?

[kimtami]

@HayesGordon Yes, the warning message appeared on the actual device, but no rendering issues occurred there. It only manifested in the simulator, though I believe it could potentially occur on real devices as well.
This is because the phenomenon didn't occur immediately after using conflicting libraries, but rather emerged after installing the Firebase library (which made finding the root cause quite challenging).
When installing the Firebase library, the following files within the iOS directory are modified:

Podfile: Firebase-related CocoaPods dependencies are automatically added
Info.plist: Configuration values required by some Firebase services may be added
Build Settings: Linker flags and framework references are automatically configured

I believe these modifications could potentially cause the ma_ios_notification_handler pointer priority to become unpredictable, which suggests this issue might also occur on actual devices.