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.
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 have created a developer account for two weeks, and now I want to submit my first App. However, when I click new app, the bundle ID list does NOT show the project I would like to submit, but It do show some projects I used to practice. I have look up a variety of solutions on internet, including sign out and log in again, or clean up my Safari data. I have suspected some reason, but I'm not quite sure if it right?
First doubt : some SDK import?
The Bundle ID shows on the list are some small project I used to practice when I was a beginner. Recently, I have tried to use some SDK like Facebook SDK and Firebase. Facebook and Firebase works fine on my simulator and iPhone devices. So I'm not quite think this might be the reason, nut just type on in case I missed something
Second doubt : Xcode version?
When I tried to using Firebase, since iOS 13.3.1 seems not to support, so I update my iPhone to iOS 13.4.1. However, the Xcode should also be updated to 11.4.1, otherwise it cannot connect to my devices. When I look up the bundle IDs listed on App Store Connect, I think those projects are created before I updated Xcode. The project created after updated not showed on the list. But I have created too many projects to practice, so I'm not quite sure I remembered right. I suspect this might be the reason, anyone else met the same problem after updated Xcode?
By the way, there is also a strange thing confused me. I have deleted some projects I used to practiced on my MAC, but they stilled shown on the list... I have manually deleted on my Apple Developer Web.
1) Go to https://developer.apple.com/account and set up the app with its explicit bundle ID.
2) Then go to https://appstoreconnect.apple.com > "Create new app" > Select the previously created bundle ID.
This does not really have anything to do with SDK usage or Xcode setup. (Automatic code signing might do some steps for you, but the most bullet-proof way is mentioned above)
I've migrated our app from react-native-firebase to #react-native-firebase/crashlytics and managed to get crash reports from Android, but no luck with iOS.
I've done all the following:
removed react-native-fabric and all of it's references
installed #react-native-firebase/app
installed #react-native-firebase/crashlytics
added GoogleServices-info.plist in xCode as described in the manual
added firebase.json in the root of the app with crashlytics_debug_enabled: true (this solved Android)
But still no success, not from the simulator nor from appCenter deployed app.
I think it's good to mention that we have 3 schemes (dev, staging, production).
Any idea how to make this work?
Chintan from Firebase. Can you reach out to Firebase Support with the bundle ids of all 3 variant? You can also reference this SO post in there. It might just need manual activation.
I've ran into quite an odd problem today. Today my app successfully got onto the app store. However, when I downloaded it I immediately noticed that the apps basic functionality wasn't working. It just hangs when trying to get outside information. I went back to my xcode project, ran it and it worked perfectly. I removed the app store version, and re-deployed the xcode version to my phone, and again it worked perfectly.
Did Apple do something to my code? The part that messes up seems to be a where my app creates a NSURLSESSION that is used to gather data from a website. Perhaps they "cleansed" the url strings that I use? This functionality that messes up is crucial to my app and hasn't been changed since I've submitted to the app store.
Anyone have any ideas why this is happening or how to fix this?
Thanks
Just posting the "solution":
Edit your Scheme and set the "Run" build configuration to "Release". After saving that, clean the project (cmd+shift+k) and run again on your device. By default, that will make you run the app in your device just as it will be ran when published in the AppStore.
And yes, unfortunately you will have to wait another week for Apple to aprove your app's new version as it will go through the review process again. Good luck! :)
For me it was that I was using old promocodes for testing.
That promocodes were from old version of the app (ios downloads app version that corresponds to promocode version), but I was expecting new functionality. So use latest promocodes!
I am not that familiar with iCloud integration. I read numerous bad reports about the integration in iOS 5 and 6. But now I guess it's better in iOS 7 so I decided to add it in one of the new apps I'm working on.
From what I read and saw in the WWDC 2013 CoreData/iCloud video I thought it was as simple as flipping on iCloud in Xcode and configuring the NSPersistentStoreUbiquitousContentNameKey value to something unique in the addPersistentStore call, to get started. But each time I run the app, in the simulator or on a physical iPhone, the console output shows the iCloud setup failed due to URLForUbiquityContainerIdentifier returning nil.
I am using Xcode 6 beta and the iOS 8 beta 2 SDK. I've made sure iCloud is signed in and otherwise functioning on the simulator and physical devices. I've also made sure that the "Documents/Data" switch is on under iCloud setting and the app IS appearing here. I've also browsed to the simulator application directory and I see the SQLite file in the normal documents directory and in an iCloud directory.
Is there something really simple I'm missing?
There is bug in Xcode 6 beta version , i am using Xcode6 beta 5 and facing same problem.
I changed key com.apple.developer.icloud-container-identifiers to com.apple.developer.ubiquity-container-identifiers" (ubiquity, not icloud). Then add an item to this as "iCloud.$(CFBundleIdentifier)". In "Capabilities" tab Xcode will show error in red mark but don't fix it , leave as it is.
If solved my problem and i am getting Url now.
Not sure what the developer agreements allows to say, but at the time of writing this, it is still beta and most probably is a bug in xcode 6. There may be a few threads on the developer forum on that exact same subject. Search for 'URLForUbiquityContainerIdentifier' and you may find more information.
Try beta 4. My iCloud code is now working.
You didn't mention configuring your app ID for iCloud access and updating your provisioning profile, so that's probably the problem. The device needs to know that your app is allowed to talk to iCloud, and it does that based on the provisioning profile. You'll need to go to the iOS developer site and:
Update the app ID to add the iCloud capability
Regenerate the provisioning profile so that it includes the new capability
Download a new copy of the profile and make sure that you're using it in testing (it's best to delete the old copy first just to be sure).