I'm trying to test user data migration from a released app (installed from App Store) to new development build.
But when I'm installing IPA on the device, I get an error:
AppName is already installed.
AppName has the same Bundle ID as AppName and can't be installed. To continue, delete AppName from your device and start again.
Any ideas, how to fix it? Thanks.
I also ran into this issue. Mine was a fairly specific case but figured I should post a reply just incase someone else runs into the same thing.
I was using Hockey, now App Center, for testing. With my last build I was unable to upgrade in place. When I would attempt to install from App Center I would see the "{AppName} is already installed. To install {app}, delete {app} from your device and try again." After trying a number of things to fix this I was never able to get it working. I instead put my app on TestFlight where I was able to upgrade in place. We ended up shipping as is and did not have any problems upgrading in the field.
My issue was a combination of both changing distribution profiles and upgrading from the Hockey SDK -> App Center in the same build.
Anyone running into this using App Center. I suggest double checking if you have the issue on TestFlight.
The iOS allows identifies app by their bundleId.
No two apps on app store can have the same bundleId
No two apps on a phone can have the same bundleId (more applicable during development)
If you use the same bundle-id, between your QA and Prod/App store builds then at a given time you can only have one app installed on your device.
Two solutions:
delete the existing app on your phone and install it again
use distinct bundleIds for different environments.
Related
I develop the app on a windows PC and then I send the file I'm using to a Mac from the company. From there I did an upload to the AppStore last week (after some problems) with a first Mac. I made some changes on the App and now I tried to upload again from another Mac. This time I am able to do the whole process without any mistakes but after clicking Distribute App and accepting everything and no Issues on XCode I get an email saying "The build status of MyApp (version) has changed to Invalid Binary". Inside the message they say the bundle id is already taken. I've checked this and on the details (Archive window) of my app I've got the correct identifier, same as in developer page from apple, and the team is also the same.
Of course all this is with automatic signing. And certificate is for distribution (I don't really know how to confirm, but this one is available)
I've got a couple questions about this.
Do builds have to be the immediate following? I mean, I can't jump from 1 to 4, for example?
I deduce version and build is always taken from the runner configuration on XCode.
Should I always submit the same folder? Instead of making new copies of the version.
On a desperate attemp of trying things I created a new version from App Store Connect plus sign in my App.
Can I delete it? Can I use the same version I named it on XCode to upload? Can I use any other named version to upload?
What else should I try? Next thing I'd do would be deleting the Bundle ID and creating a new one, but that doesn't solve my problems on the long term.
I am using:
XCode 13.2.1
macOS Monterey 12.2.1
I tried changing versions and builds on Xcode, expecting to create the correct one.
I tried from an old mac to see if it was that I haven't got the good certificates, expecting a correct upload.
I'm trying to conceptually understand how I broke my push notifications in iOS 9.
Here's what actions I took:
I updated the Parse and Bolts frameworks from 1.6.1 to 1.8.3 by deleting the old frameworks in Xcode and deleting the actual files in the finder. Then I added the new versions of the frameworks into the project by dragging them into Xcode. I checked the build phases and the new libraries are linked.
At this point I tested the app and was not receiving notifications with this build. People running previous versions of the app on iOS 9 do receive notifications.
I had not changed the App ID or Provisioning Profile at this point, but I thought they could be the issue, so I created a new Provisioning Profile with the existing App ID. Still no notifs.
I checked in Parse Core and my device is registering with the correct build # and the updated Parse library. So Parse knows my device needs to be sent a push, but it's not getting there.
Normally I would expect the advice to be create a new Provisioning Profile, but I did that. Any idea what I might be missing here? Thanks.
Since you did all of that, I would like to note that Push notifications are not guaranteed to be sent, they just usually are. And Parse Push has gone down before. So if not tonight, try again tomorrow. However, I would try a couple more things, ensure your client-push is enabled in your Parse.com console. I would also delete the app and reinstall and also make sure your code signing is accurate in your project settings. You should also try a simple Clean in Xcode, sometimes that does a lot of good. At most, you could try building an Ad Hoc version to test. Lastly, they have summarized a couple of more things you can troubleshoot since this a common issue and they use their Google Groups for developer communications now more-so than SO : https://groups.google.com/forum/#!topic/parse-developers/65WAfRIiEnA
Note: This is not a one-answer fix, since push notifications don't have a one-specific issue. But these are general outlines of what can be done to remedy your particular issue. I have two apps with Parse, running Xcode 7 GM and iOS 9 GM and push notifications are working for both.
Simply using an ad hoc build (ie with production push certificates) rather than deploying from xCode (with development certs) resolved this. If your app is already deployed in production in Parse, you will have replaced the development certs in their dashboard when you released it.
I have very weird distribution scenario with the iOS app.
App works normally in simulator
App works normally on the device with developer profile (and corresponding bundle id domain.product)
When downloaded from testFairy service with valid enterprise provisioning profile app and bundle id (in form domain.beta.product) app:
Installs without error
Shows lunch screen and terminates immediately
When I connect device and check logs through Xcode -> Devices -> Show log I don't see any today's crashes, like no error happened. (this confuses me the most)
This happens on 2/2 iPhone devices that tried to run the app.
Some other infos that could maybe ring a bell to someone:
- App uses Core Data
- App uses TestFairy SDK (but it was the same without it)
- target is iOS 7.0, base SDK is Latest iOS(iOS 8.1)
- provisioning profile is set to that Enerprise Profile and signing identity is set to corresponding certs for both debug and release.
- I've removed armv7 from Targets-> Info -> Required Device capabilities as suggested on some stack overflow solutions.
Anyone experienced similar problem? What could be the cause?
I work for TestFairy, I think I can assist.
Few points:
TestFairy's distribution does not alter the IPA in any way.
When using an enterprise profile, you need to sign using (TEAM.domain.company.app) in your application-identifier. iOS 8 shouldn't let you install if the identifier does not include the TEAM.
If the app crashes immediately (with or without the Default splash screen,) it might be because you're out of memory. Does rebooting fix the problem?
Can you please paste all the logs from right before the launch, till the app exits? you can attach and send to TestFairy's support (via Contact page.) That would be helpful. Also, if you're interested, you can email support with your username and link to build, and they can try installing it on their devices and let you know what the problem was.
My application got stuck on installation due to wrong configuration on my iPhone with iOS 7. Provisioning profiles, certificates, devices everything seems ok.
I found an example of how to prepare a web page to provide a download link for your iOS application. I completed the necessary steps with one small mistake. The mistake was my appName.ipa and appName.plist was different.
As a result, the link was look like working but was installing 2 apps because of this difference. Real app finished installing but other clone that comes from the wrong .plis file never finished installing.
I'm able to install/remove application but this second clone cannot be removed even there is an (X) symbol in edit mode. When I press the (X) symbol for deleting it shows the Alert View but not deleting the clone even I press Delete or Cancel.
I tried to delete it but couldn't find a way. I currently don't have any issues installing/removing my application but it just stuck there. Is there anyone has the same problem before or any ideas?
Did you try with iPhone Configuration utility (Win) / iPhone Configuration Utility (Mac) ?
I realised the problem, it's about the Bundle Identifier difference. I created a new app with the ghost icon's bundle identifier and run it from XCode, so XCode overrode it and successfully installed the test app.
We've built an MDM server using a mac mini.
We have 2 applications to push out to a number of users. One app will push and download on the remote devices with out a problem. The other displays an error "The app could not be installed at this time"
This second application is an older application.. however we are building it for 6.0. In the console we see this.
ipad SpringBoard[65] <Warning>: could not save thumbnail for downloading icon: image=(null) path='/var/mobile/Library/SpringBoard/DownloadingIconImageCache/
This app can be built an installed when a device is connected to the build computer. We have all of the signing the same as the first application. We can also archive the app without any errors. What would cause this app to not install, or what should we start with?
Several notes/ideas:
a) Take a look at this (they mention the same problem)
Trouble installing AD-HOC distribution through safari
iOs application crash on install
Ad-hoc distribution fail
http://community.phonegap.com/nitobi/topics/not_installing_my_application_in_ipod
b) Can you please post your manifest (if you are installing inhouse apps)?
Please double check that that if you pointing to icons in this manifest, the links are correct.
Ok this took days to figure this out... In my situation at some point another icon was added into the build settings. We did change the name of the bundle so I'm assuming that xcode automatically populates the icon information?
In the info tab check to make sure you only have one property for 'icon files' (to be clear you should have the ability to open the drop down menu and expose sub menus... What I had was 2 'icon file' sections.) After I deleted the second set of icon files it pushed fine.
Hope that helps others figure out a very frustrating situation