Closed mylegfeelsfunny closed 6 years ago
For a little insight, it looks like the config url is losing the in iOS 11.
https://config2.mparticle.com/v4/(null)/config?av=2.0.0&sv=6.15.16
is what gets set.
We were able to narrow down the search to MParticle.sharedInstance()
fetching the configuration before start(withKey ...
is called on iOS 11.
Because it is called too soon the url is malformed. Perhaps this should not happen.
Hi @mylegfeelsfunny - all of our customers have apps running on iOS 11, many with kits. There is likely something that's specific to your implementation causing this. Please work with our support team and we'll get this resolved through that channel. Thanks!
We are also experiencing an issue with the Adobe Kit not working in our app running iOS 11.2 We are unable to send outbound messages to Adobe Marketing Cloud. The outbound connection is working in iOS 10.
SDK versions: mparticle-apple-integration-adobe.framework binary at "Version 6.15.17" mparticle-apple-sdk.framework binary at "Version 6.15.17"
Hi all - this should have been address in release 6.16.1 yesterday, and will be address in 7.1.1 today. Please let us know if you're still seeing this!
mParticle.start(withKey: XXXXXX, secret: XXXXXX, installationType: .autodetect, environment: environment, proxyAppDelegate: false)
is activating theAppsFlyer
andBranchMetrics
kits fine in iOS 10. We are observing themParticleKitDidBecomeActive
andmParticleKitDidBecomeInactive
as usual. But when compiling with iOS 11, the notification are not posted. In fact, the start methods of those kits are not called either.Am I missing something obvious in the docs?
We are also using
use_frameworks!
in our podfile but have the recommendedCode base is 99% swift minimum Target is iOS 9
We are losing all of our AppsFlyer campaign data, so it is pretty urgent for us. Thank you in advance.