Since the upgrade of my devices for iOS 8, I keep having a Window Alert for Push Notification even on applications which haven't such notification : "MyApp Would Like to Send You Notifications"
After research, I've seen that it may be caused by an old AIR version.
Problem is that I'm already testing in the last AIR SDK version ( 15.0.0.249 ) and the push notification keep appear.
Otherwise, the real problem seems to be that in my others applications which allready have the push, it seems to make conflict when you refuse the push at the first opening. It cause freezing the application and force to kill it.
Does anyone have a clue ?
Thanks a lot,
Update to the AIR 15 beta. This bug was fixed a week or two ago (though I can't find the release notes saying it was). The betas are stable in my testing and fix a lot of iOS 8-related issues.
http://labs.adobe.com/downloads/air.html
Related
have you had the following error in TestFlight? Basically, we have test versions in TestFlight that when we launch them to external testers work. But it has happened to us 2 times that after a week or two, that version stops working.
Basically, the app won't open, won't even show the splash, and crashes.
Last week the app stopped working for all testers, we updated to a new version and it started working fine for them again. But yesterday the version that already works previously began to fail them again.
Today, I just generated a new version with no code changes and it works. But I'm afraid it will eventually start to fail.
When I say that it fails, it is that the app icon is touched, it tries to open, but it does not open and it crashes.
For example, now the new version works fine for me, but if I go to TestFlight and install a previous version that worked fine on my phone 2 days ago, it no longer works for me.
Any idea what could be going on, guys?
Maybe some certificate expires or I don't know, any idea is welcome.
I'm using expo managed workflow and eas build to generate the iOS app.
Something that happens with the versions that start to fail is that when they are installed, the first time it does not fail. But if I completely close the app and reopen it again, it doesn't open anymore, and the crash occurs.
We're using Sentry, but we don't have any issues. But I have this crash in TestFlight errors.
Thank you in advance for all your comments or ideas.
Can I still upload an application that does not support iOS8+?
I currently have an app that we are releasing for iOS7 and 7.1, but it was rejected because it was not compatible for iOS8.
We are currently in the process of building the iOS8 version, but wanted to release something quickly.
You just need to build & submit it with XCode 6, iOS SDK 8.0.
They may reject if the app doesn't work with iOS 8. Do a quick test to make sure it doesn't crash, and all major functions are working fine.
No you can't. I'm not sure the exact date that apple made it mandatory to support iOS 8 but I do know it has passed so any new apps/updates submitted to the app store need to support iOS 8.
We have just released a new version (v1.5) of our app on AppStore, this version was built using Xcode 4.6 using base SDK 6.1, supporting iOS 5.0 as minimum version. Now the problem is that iOS 7 users are unable to install the latest version (v1.5), however they can see 1.5 version on AppStore but when they install it they get 1.4 version.
Note: We submitted this app using Xcode 5.0 as Xcode 4.6 just got stuck in the middle...
Apple is currently reviewing apps with iOS 7 devices. So they have (with very high probability) reviewed your app on an iOS 7 device.
If the app has been recently released, then it may only be that servers need some time to refresh. If it has been a long time since the app was released (more than one day), then you should contact Apple support and ask them to see what is going wrong with their App Store system.
Unfortunately the issue was sporadic, it happens with those users who use "App Store" mobile app to install our application. App Store displays latest version in the App-Store app but when they install it they get a previous version on their devices. Then again if user launches "App Store" he is able to upgrade to the latest versions. This issue doesn't effected our existing customers but the new one (those who have deleted the app from their device also experienced similar issues). We had a long conversation with Apple on this issue over emails, finally they admitted that it was due some problem at their end.
Now it is fixed for our app and we no longer have this issue for current release. I hope this post will help to someone having similar problem.
I am trying to download applications from my Worklight Application Center Client (5.0.5 version) on an iPhone 5 runnning ios 6.1.2.
9 times out of 10 the download and install of the application will fail, whilst 1 in 10 times it will download and install correctly.
I have also tried using an iPhone running io5.1 and the install works fine. It also works fine on an iPad running ios5.1. It fails on another iPhone running ios6.0
I have checked issues such as signing of the apps and if I am using a correct UDID and I can say that these are not causing the issue, especially when you consider that it works some of them time.
It seems to be something to do with ios6 specifically.
Has anyone else seen this kind of behavior or can offer any help in terms of resolving it?
Thanks in advance,
Joe
The situation with iOS 6 seems better with Worklight 5.0.6, to be released in the near future.
I've installed Testflight (1.2 B3) as stated in the documentation. Builds are uploading and updating fine. I can see sessions (mostly anonymous :/), I receive the logs (TFLog) - but I do not receive any crash reports. I even introduced a crash-on-event (a method not found thing) - but theres is nothing on Testflight about it.
Provisioning is via a developer profile which embeds several devices.
The problem occurs on iOS6 and iOS5 / iPhone5 and iPad3. The is being build against iOS6.
Any ideas?
UPDATE
I've tested several other frameworks and ways to receive crash reports. Nothing worked so I suspect something in my code (obviously). Are there any other switches that XCode 4.5.1 might have enabled and that way disable any error reporting during a "production environment" like setup?
UPDATE 2
As of now we're using Testflight only for distribution of beta versions and switched to Crashlytics for crash reporting. It's a bit more streamlined and fetches most crashes.
I also do not get any crash reports via TestFlight. This is what the TestFlight people told me:
Our team is currently looking into an issue associated with auto
versioning of the app when uploaded and SDK data not reporting
properly. Looking at the URL you provided it looks like the build
version is not changing before uploading the app to TestFlight and our
auto versioning implementation is causing an issue with general SDK
data reporting.
I will share this with our team and we will contact you when we have
an update available.
I tried to update the build version to avoid auto-versioning, but it did not help me. But maybe this issue is hitting someone else.
Testflight did not satisfy our needs to log crashes. That is why we skipped to Crashlytics (as I said in the original post). The issues with Testflight seem not to be resolved. We still do use it for distribution, that is what it's good at.