suddenly after adding a group to the App Groups section for my Watch extension and iPhone app, I can no longer put any app on my device, All I get is the folowing error:
"The application does not contain a valid application-identifier entitlement"
has anyone encountered this and solved it?
(System is as folows: 10.11 + Xcode7 + iOS 9 + watch2) == full beta os nightmare.
I ran into the same problem. Still OSX 10.10 here. My colleague already has 10.11, he had no problem developing, but I can't deploy anything on the device anymore (iOS9/watchOS2) - both as normal development built, nor as adhoc built. what I still can do (using xcode6) is upload to the appstore and use testflight. however, there's a testflight problem on my device ("can't currently be installed"), so even there I fail.
Did you find a solution already? I'll keep you posted when I found one.
Best
-H
I have the same problem but not sure what the problem is
Anyone have any luck? This is a horrible show stopper for me and I'm not sure how to proceed. I'm using OS X 10.11 and iOS 9 beta 1. Everything has gone great with Xcode 7 until I tried to use my real device.
Same here. Any new information?
I've encountered the same issue and found a workaround. As TestFlight confirmed, the build did have an application identifier, but digging into the device's logs I noticed that there was an application identifier mismatch with the already installed version of the app. So I deleted the app on the device, and then build & run worked and the error went away.
I am running into something very similar. This the the full error that I get:
"This application's application-identifier entitlement does not match that of the installed application. These values must match for an upgrade to be allowed."
This only started happening when I started to update my app to a WatchOS2 app, and allowed excode to try and migrate my existing app for me. I can run the app in the simulator just fine and this only happens when I try to build on the actual divice.
Same thing here .... Is this a real bug or something we miss in the settings ?!
