Duplicate Simulator Libraries listed in Flurry-iOS-SDK.xcframework/Info.plist

[mattwylder]

Describe the bug Flurry-iOS-SDK.xcframework/Info.plist has two AvailableLibraries with the identifier ios-arm64_i386_x86_64-simulator: item 1 and item 6 in the AvailableLibraries dictionary. There is no available library for ios-arm64_armv7. Building for device and simulator does not work for version 12.3.1.

This Bug is About Please choose the closest item by replacing [ ] with [x].

• [x] Integration
• [ ] Analytics
• [ ] Ads
• [ ] Messaging/Push
• [ ] IAP
• [ ] Remote Configuration
• [ ] Flurry Website/Dashboard
• [ ] Other

Platform Please choose the platform(s) that you are having the issue by replacing [ ] with [x].

• [x] iOS
• [ ] tvOS
• [ ] WatchOS

Environment Please tell us the versions of Flurry SDK, XCode, and iOS you are using.

• Flurry SDK: 12.3.1
• Xcode: 14.3
• iOS: 16

To Reproduce Steps to reproduce the behavior:

1. Create an empty new Xcode project.
2. Drag Flurry_iOS_SDK.xcframework into the project
3. Attempt to build for the simulator. You will receive an error: A library with the identifier 'ios-arm64_i386_x86_64-simulator' already exists.
4. Attempt to build for a physical device. You will receive the same error.

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Are you using Flurry Push/Messaging? No (iOS) Are you using CocoaPods or manual binary integration? Yes

Add any other context about the problem here.

[flurrydev]

Hello Matt,

Thanks for the report. I wasn't able to reproduce the issue you described in a quick test on simulator and iphone. Note the Info.plist you described does not match the one posted here for 12.3.1:

https://github.com/flurry/flurry-ios-sdk/blob/br_12.3.1/Flurry_iOS_SDK.xcframework/Info.plist

Here is a more readable view:

Has your copy of the xcframework been modified? I'd like to get to the bottom of this issue.

Thank you, Hunter

[mattwylder]

Hey there 👋 . I cloned the branch in fresh from master yesterday. Should I be pulling from a tag instead?

Here's the version on master

[flurrydev]

Yes use the 12.3.1 tag or clone the br_12.3.1 branch.

Thank you @mattwylder