Closed dchersey closed 8 years ago
update: adding
app.development do
app.entitlements['get-task-allow'] = false
end
"fixes" this issue but now I won't be able to use the debugger in development. How can I specify this only for fabric uploads?
Sorry for the delay, I did not see the notification for this issue!
Thanks for the detective work. We should definitely remove that entitlement inside motion-fabric
.
Meanwhile, you can add that piece of code inside the config.beta
block so it will only be used for beta builds:
app.fabric do |config|
config.beta do
app.identifier = "my_identifier"
app.codesign_certificate = "my_certificate"
app.provisioning_profile = "my_ad_hoc_provisioning_file"
app.entitlements['get-task-allow'] = false
end
end
Leaving this issue open until we fix this inside the gem.
Just published motion-fabric
0.5 fixing this. Thank you!
Hi,
I've integrated motion-fabric, set up an account, and am successfully using it with Crashlytics. I've just started using it for beta distribution and I am running into a problem installing the beta builds on any of my test devices.
After a lot of research, I found that the entitlements.plist is being generated with
This is what rubymotion does for development builds, and motion-fabric seems to be using a development build.
However the ad-hoc distribution provisioning profile does not allow this, resulting in the following error on the device log while installing:
I suspect there is a simple solution here somewhere -- perhaps I can tell motion-fabric to use a release build? I don't see anything in the doc that would specify this.
Any help would be much appreciated!