问题
I'm running into problems getting Branch to work for deep linking. My thought is it's because of the app prefix.
I go to the developer portal and create a new app id:
Then I create a new provisioning profile using that app id:
When I go to set my prov profile and dev cert the prefix do not match:
So I'm guessing that the app is being compiled with a different prefix than what's in the provisioning profile. So when I try to deep link from Branch, it's not finding the app.
I've tried creating new certificates, new provisioning profiles, new app id's. Nothing fixes this. Any ideas?
回答1:
Alex with Branch here: yes, the provisioning profile mismatch would definitely cause Universal Links not to work! However it shouldn't have any effect on URL scheme deep links. Are both broken right now?
It's tough to troubleshoot exactly where the provisioning profile configuration is off without access to the project file, but here is the Apple docs page about all the places it can be set: https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/ConfiguringYourApp/ConfiguringYourApp.html
回答2:
Turns out, Universal Links do not work with Branch test keys due to the limit on the size of the AASA file imposed by Apple.
So, if your Universal Links do not work and you're using test keys, that's probably why. Also, make sure that the url you're using doesn't contain /m/ as that's not a Universal Link.
来源：https://stackoverflow.com/questions/36915775/provisioning-profile-prefix-different-than-that-it-compiles-with