I'm experiencing a very weird issue with my app:
I'm going about the standard way of detecting a shake event. I have implemented the canBecomeFirstResponder method, and I call becomeFirstResponder in viewDidAppear and resignFirstResponder in viewWillDisappear. Then I implement the motionBegan method to handle the shake events.
When I build and run my application onto my device through XCode, everything works great. The motionBegan event fires and my program properly handles the shake event. All good, so I submitted my application. I was shocked to find out that when I downloaded it from the App Store, that my shake events weren't working! Now, in trying to fix this problem, I've also found that it doesn't work if I archive my app as an .ipa file and then load it onto my phone through iTunes.
In short, the shake event fires through a run on XCode, but not when it's been put onto a device via distribution methods!
This doesn't make any sense to me so I'm really hoping someone knows what's wrong!
PS - this issue occurs regardless of how application.applicationSupportsShakeToEdit is set.
I'm going about the standard way of detecting a shake event. I have implemented the canBecomeFirstResponder method, and I call becomeFirstResponder in viewDidAppear and resignFirstResponder in viewWillDisappear. Then I implement the motionBegan method to handle the shake events.
When I build and run my application onto my device through XCode, everything works great. The motionBegan event fires and my program properly handles the shake event. All good, so I submitted my application. I was shocked to find out that when I downloaded it from the App Store, that my shake events weren't working! Now, in trying to fix this problem, I've also found that it doesn't work if I archive my app as an .ipa file and then load it onto my phone through iTunes.
In short, the shake event fires through a run on XCode, but not when it's been put onto a device via distribution methods!
This doesn't make any sense to me so I'm really hoping someone knows what's wrong!
PS - this issue occurs regardless of how application.applicationSupportsShakeToEdit is set.