Push notifications not working after portal changes - iphone

I recently changed the following things on our Apple Dev portal. I asked this before but wasn't very clear on what I had changed.
I'm using:
- Phonegap 2.1.0
- iOS 6 min 4.3
- XCode 4.5
I am using only development certificates for testing. We aren't testing the production certificates yet.
App ID's : Enabled Production Push notifications.
Provisioning: Added a distribution entry and removed 1 device from the profile.
I also changed the Product/Bundle Name in the main target.
I downloaded the new certificates and installed them.
I get a token perfectly, it registers for notifications. I don't get an error from Apple feedback. Is there anything that I changed that would effect push notifications? Would I ever have to re-download anything but the provision profile after making changes? I'm testing on an iPhone 4, I've rebooted several times and switched notifications on/off.
I also added the AppStore build scheme if that has any effect.

Well they started working after I changed the Bundle Display name back to the original name, but I don't think that's what fixed it, I had done that before.

Related

How to deactivate an app once in production - can code be added?

After a tiring 3.5 months I learned how to build and launch an app using Flutter and Android Studio. I tested in debug mode on various emulators and all worked well.
I then built the app bundle and uploaded on to Google Play Store as an internal release - again everything ran well.
I pushed this in to Production. After a week of waiting for a review, the app launched. I uninstalled the test version and installed the live production version - and that's when the problems started. The app began to crash in places it hadn't before. Namely on certain pages (and often after the render of certain pages the app closes after c.3 seconds) or upon button presses on certain pages.
I have now added Crashlytics to the app (which I didn't have before), and have pushed this as a second version on to the Google Play Store - and again it's pending review. The questions I have are:
Can I deactivate an app once it's live on the app store to prevent any more downloads? - Is there any code that can be added to the app to do this internally? I can not see any options or instructions within the Play Store. It seems a little crazy that I now know my app has 'bugs' which never materalised in test, but i can't 'switch it off'?
I have only been able to add Crashlytics this time for a new production release, and once installed and I can try and work out what the problem is with error logs. Once I have I will have to create a third version and again add as a new release and wait for Google to approve - is this really the most efficient way?
Why would or could a Production release of an app crash when the Debug version, or Production release version in Internal Test mode, did not? - I find it so strange that I have so many tools available and yet none detected a problem until launch
Thanks in advance!
you can unpublish your app from playstore
goto console>select your app>setup>advanced setting>unpublish app
this will stop your app from appearing to new users and getting new download from
playstore
2.fixing bugs always need a new release to update your app there is no way to get around
uploading a new release and waiting for the review to end (this is for production app)
3.your testing might not have encountered any bugs because you might be testing on one
device or emulator with a specific api for example api 30 ,and the bugs are being
detected on other apis or device properties you haven't covered in your testing

Codename One Push Notification

We are trying to implement Push notification on one of our apps.
For Andriod, we registered with Firebase, downloaded the google-services.json file and added it to our native/andriod directory.
On the Emulator everything works fine, but on an Andriod device the Push Registration fails with Error code 0, INVALID_PARAMETERS as given by the pushRegistrationError callback method.
For iOS, we are trying to generate the Push Certificates using the iOS Certificate wizard on the Codename One Plugin for Netbeans.
On the step where you should select Enable Push, the tick is unavailable.
We have upgraded to the Professional Subscription so the little note of Pro Feature Only is a bit weird.
Any help will be great!
You need to login again in Codename One Settings for this to work, notice your email account and pro level should appear in the Codename One Settings UI. If they don't you might be running into a known bug for which we have a fix. We will release an update to the Codename One Settings app this Friday with the fix for that bug.

How to simulate the AppStore update process on device/simulator

We have submitted an update version of our existing applications in the App Store recently. But we have received a issue from one of the users, saying that the app is not functioning properly after the update. So in order to replicate the same, what are the steps to reproduce, so that i can analyse the issue?
Any help will be appreciated.
To simulate this before pushing yoru updated version to the AppStore you can:
Download the old version of your app from the appstore
Run the updated version of your app from XCode on the same device.
What will happen behind the scenes is that your app will be updated in a way similar to the Appstore. Your app will be partially updated while your doucments folder will stay the same. (what usually causes problems)
This solution is better because it lets you check for problems before and update was pushed to the Appstore.
Yeah, I get this a lot. The solution is a bit annoying, but you need to keep a history of IPAs you've submitted so you can put the on your phone through iTunes (so not the simulator) and then, run your code on your device putting a breakpoint on your applicationDidFinishLaunching handler in your app delegate, and start tracing from there. You should be able to find the old app store version in your organiser from the last time you submitted, or, go through your SVN/GIT history and checkout the version tagged to your release version.
Many times in the past that has happened to me where I test a new revision and everything looks fine but when I submit an update and is approved, users start complaining about a crash or lost data.
This is way I approach the problem.
(This is most important step) You need to either have your old code or old binary installed on your actual apple device. (Physical iPhone / iPad)
Now go to iTunes and install your new update.
Attach your physical iPhone / iPad to you computer, Launch Xcode and start debugging it.
NOTE: There have been many times when things work perfectly in the Simulator but break on the actual device. Its always important to test your code on the real thing as that is what the users are going to be on.
All that is required is to have the version of the app that is in the app store on your device, then install the updated version to your device. You can debug it using Xcode when you install the new version.

Push notifications not receiving on device

I am using APNS service in my universal app (iPhone/iPad) and i am not geting notifications on device. Previously i was getting notifications perfectly but now a days with the same code at server side and client, it is not working.
On server side notification status is delivered but i am not receiving it on my device.
I have checked most of the questions on stackoverflow but i was unable to find my question. one guy said that in development environment it may have delays, but my problem is that i am not receiving notifications at all.
Note: i am using sandbox environment not production.
Just in case you haven't found a solution yet, one additional thing you could check is if your device's date and time is properly set (in the OS). If your iPod, iPhone or iPad isn't set to the current date, we found that notifications are ignored silently. Of course, there are many other possible explanations as to why your service stopped working, but this is a simple thing to check when everything else appears to be fine.
Following are the things you can check
Check the entitlements while codesigning the app. (They can be seen in Xcode build log).
Check whether notifications are on for the device in the settings menu.
If you are using corporate network on the iOS device, the push notifications might be blocked. Try using a different network.
After launching the app, check the organizer for any logs with the reason why push notifications can not be enabled.
I hope some of this helps you out.
I just revoke my certificates
Uploaded new certificates deleted all provision from my organizer
and then created new provisions and installed them on my system.
At the same time I got my APNS working.

Anyone else having problems installing iPhone Enterprise apps on released IOS 5?

Anyone having problems deploying Enterprise apps on iPhone/iPads running the released version of iOS 5 using the OTA ("over the air") methodology?
During the installation process, we get the alert box: "the app could not be installed at this time". Tapping the Retry button does nothing. In some cases, repeated tapping of the Retry button eventually results in a gray, empty launch icon being left on the home screen. No app installed. No other errors.
Anyone else seeing this or have a resolution?
The below description is a bit involved, but please bear with me as it may help others who run into the situation. I will post the resolution if get a resolution from Apple. So far, no joy there.
Our app refuses to install OTA on iOS 5. This same app WILL install on iPhone/iPad devices running iOS 4.x.x AND the same app will install on iOS 5 devices physically connected to a desktop machine using the iTunes app.
The Apple Developer forums under the IOS 5 Beta category complained about the problem but no indication of resolution as of last week just before the official release of iOS 5.
Cookies are set to be accepted.
Bowser cache and history cleared.
Using mobile safari originally installed with original iOS version 4.x.x.
System hardware and operating system configuration
iPad 2, iPhone 4 or any iPhone device running iOS 5 RELEASED version.
Browser and version
Mobile safari that is installed with iOS 4 on ipad2. Don't know if mobile safari upgrades with ios 5 upgrade.
Using a corporate wifi network. Yes, we are behind a firewall and use a proxy server. Since iOS4 devices install without problems, I don't think installation being blocked by the proxy or firewall.
Enterprise app built with Xcode 4 and ios5 sdk provided with it. Built to be backward compatible with iOS 4.0.
Distribution provisioning profile is correct as we have been using it for several weeks.
This app installs properly on iOS 4 devices both over the air and via iTunes application method.
This app installs properly on ios5 devices through the physical connection with iTunes application on the Mac desktop.
Steps to reproduce:
User types in the URL in mobile safari on iPhone/iPad running ios5.
The resulting webpage shows the download app link.
User taps on the link and is asked if they want to install the app.
User taps the yes, install button.
App proceeds to install.
A gray launch icon shows up on the home screen with the progress bar empty at the bottom of the icon.
Message below the icon indicates "loading".
Seconds later, user gets the "cannot download app at this time" error message as seen in screen shot attached.
Tapping the retry button results in the same action just described.
Tapping done results in the download stopping.
If you tap retry several times, user sometimes is left with the gray empty launch icon, which will not launch and cannot be deleted.
Note: In the apple developer forums, under the iOS 5 beta category, people are describing the exact same problem with no resolution.
Had the same problem, and was able to resolve it. However, the error noted is not specific to a single cause that handles every case... some detailed investigation needs to occur.
Your best bet is to connect the device to your Mac, and using the Organizer of xCode view the console logs while you are attempting to do a wireless deployment. There will be some useful information available -- please post the logs.
For my case -- the icon files were missing from the build, as a result of moving from xCode3 to xCode4 and also, the distribution plist was referencing an image that returned a 404. Both were logged in the console, but not very clearly.
Also, as a sanity check, manually verify the URL to your IPA file also.
I had this same problem and was sure everything was correct in my project; but restarting Xcode and doing a clean revealed my Enterprise scheme had somehow defaulted to the wrong provisioning profile.
Re-selecting the correct profile and re-archiving the app fixed the issue for me, I'm able to install an enterprise app on both iOS4 and 5.
I wanted to chime in after fighting this for a few hours. It is iOS 5 specific.
We had an htaccess password protection on the directory. Removing this allowed the app to finally download. So if you have htaccess, perhaps you can point the user to a parent directory that is password protected, then navigate to the subdirectory containing the app that isn't password protected. This is a temporary solution, apple needs to fix this.
Another thing to consider is the URL you specified in your over-the-air Application.plist file. I received the same error message ("-application- could not be installed at this time") because the URL I specified was too unspecific. Rather than writing "directory/directory/application.ipa", I had written "directory/directory/". You must include your application in the complete URL of the plist file's configuration.
If you didn't do this, don't fret! You don't have to rebuild the entire thing from step one, you can open your .plist file in any standard text editor and simply change the URL.
We had the same thing.
Our mistake was to point to a wrong 512.png icon in the manifest.
Which was no problem on iOS4 but turned out to stop iOS5 into a "...at this time" alert.
Wanted to chime in on my experience.
In my case, we were changing the address where the IPA file was hosted. Although I updated the PLIST file with the proper URL to the IPA file, iOS was still going after the old URL almost as if it cached the PLIST data. Creating a copy of the PLIST file and renaming it resolved the issue (data within the file remained unchanged)
I met the same problem today. The app can be installed in ios4, but failed in ios5 with "** could not be installed at this time" alert.
According to patricksan's suggestion, I download iPhone Configuration Utility 3.5 for Mac OS X, and try to catch the log while install the app through OTA.
The log helped me finally, one sentence of the log says entitlement 'get-task-allow' has value not permitted by a provisioning profile. It remind me that if the code signing identity in build settings of Project and Targets are correct, after checking them in Xcode, I found the code signing identity are not correct one, they should be iPhone distribution:.... other than iPhone developer:..... After correcting them, and re-Archiving the ipa file, it can be installed in iOS 5 now.
Check your Info.plist for Required device capabilities property. I recommend to delete completely this property if you haven't any restrictions on use.