AppLovin / AppLovin-MAX-Swift-Package

AppLovin-MAX-Swift-Package
8 stars 10 forks source link

Build looking for bundle in wrong directory/path #3

Closed WiseKodama closed 6 months ago

WiseKodama commented 9 months ago

Greetings,

I have added AppLovin SDK via swift package manager, however I am running into the following error when trying to build. It seems that it's trying to grab the bundle from the build directory, if I copy and paste the AppLovinSDKResources.bundle into the path where it's searching and modify the name to AppLovinSDK_AppLovinSDKResources.bundle, then build will succeed.

Is this a bug or an oversight of the integration on my end?

image
ritamsarmah commented 9 months ago

Hi @WiseKodama,

I just tried out a build with SDK 12.1.0, but unfortunately could not reproduce the error you are seeing. Here are some initial troubleshooting steps I'd try:

If the above steps didn't work, could you share which Xcode/Swift/SDK version you're using for your project? If you're using a Package.swift to manage dependencies please share that as well. Thanks!

WiseKodama commented 9 months ago

Hi @ritamsarmah

I am using Xcode 14.2, Swift Language Version 5, SDK version 12(Next Major version), targeting iOS 12.0.

I am not using Package.swift, instead it's added directly onto project:

image

Tried with a new project and it worked without issues, however I still need to somehow solve it for the current one. Is there anything that could be modifying the search path for the bundle somehow? Full disclosure: I am not an iOS dev, I am a game dev, trying to push an update to a 10 year old game.

ritamsarmah commented 9 months ago

Got it, thanks for that info. There may be some build setting that's causing the issue as you suspect, but it's hard to predict what that could be with the current information we have.

Would you mind sending your project via email to ritam.sarmah@applovin.com so I could inspect the build settings myself?

ritamsarmah commented 6 months ago

Hi @WiseKodama, if you have any further information, let us know. For now, I'm closing this issue out since we've not received any similar reports, so it's likely related to your project-specific build settings.