I am getting an error while trying to release the application for Apple App Store.
Error ITMS-9000 Invalid segment alignment
Following the process flow mentioned on the link below:
http://www.raywenderlich.com/8045/how-to-submit-your-app-to-apple-from-no-account-to-app-store-part-2
I am stuck with this for quite sometime now, any help would be greatly appreciated.
The SDKs and the framework details are as follows:
Flex SDK 4.12.0
Apple IOS 8
Adobe AIR 16
I have also mentioned the question on Apache forum but haven't received any reply
http://apache-flex-users.2333346.n4.nabble.com/IOSApp-rejected-Error-ITMS-9000-Invalid-segment-alignment-td9409.html
Use 4.14 SDK with AIR 16.0 version It will solve all the Issues.
Related
I am using Xcode 12.5.1. I am trying to run a simple Apple Watch App. I am getting this error.
error HE0046: Failed to install the app
'com.companyname.Abc.watchkitapp' on the device 'watchOS 7.4
(18T187) - Apple Watch Series 6 - 44mm': ???AbcWatch.WatchOSApp???
Needs To Be Updated
I have tried to find a similar issue on the internet but I couldn't get any. What would be the issue ? Please help me out.
I am seeing the below error in iOS 13 when trying to setup an app with universal links. Has anyone seen this or know what it means?
I am seeing this error in the device console for the swcd process.
Error getting enterprise-managed associated domains data. If this device is not enterprise-managed, this is normal:
Error Domain=SWCErrorDomain Code=1701 "Failed to get associated domain data from ManagedConfiguration framework." UserInfo={NSDebugDescription=Failed to get associated domain data from ManagedConfiguration framework., Line=250, Function=<private>}
When I install the same app on an iOS 12 device it works perfectly fine. Any thoughts would be appreciated
It seems that upgrading to iOS 13.2.2 solves the issue.
There is no official confirmation about this, but is seems resolved on iOS 13.2.2.
There may be some different places that cause this problem. Note that the format of AASA file seems to be changed recently. Please refer to this.
If the delegate isn't called, and there are some Google Analysis or Firebase features in the app, then it may be caused by method swizzling. If that's the case, please refer to my answer here.
I've developed an iOS app that uses the url(forPublishingUbiquitousItemAt:expiration:) method of Apple's FileManager class. Starting with the first Beta of iOS 13 this function stopped working and now it throws an error, stating "This code has been removed. You should switch off of this SPI". But I can't find anything related to this function neither in the release notes of iOS nor in the documentation for this function, and it even states there that it would be supported on Mac Catalyst 13.0+.
This also has nothing to do with Xcode 10 and 11, as it occurs when the app is built using either one of those versions.
Does anyone of you know more about that? It would be great to get new information on that.
Thanks,
Fabian.
This is fixed in iOS 13 beta 6. Updated today and this error magically disappeared!
Had my mind blown when I saw this error message.
I have created a game for iPhone in Swift (Xcode 6.4) and there is no error message in Xcode. Everything is working correctly in Simulator and also on real iPhone. Problem is after submitting the package to the iTunes Connect.
I alway get error: 2.1 - Apps that crash will be rejected.
"We were unable to review your app, as it crashed on launch. We have attached detailed crash logs to help troubleshoot this issue."
Logs:
http://a52.phobos.apple.com/us/r30/Purple1/v4/fc/77/53/fc7753f6-9d9d-991d-8c02-c1afeae66ea2/temp..ojahvbgy.crash?downloadKey3=1438984413_5da87ab807d97290498f8dbabc60dec7
and
http://a1313.phobos.apple.com/us/r30/Purple1/v4/7d/79/b2/7d79b24b-e816-0c34-8f51-d9775024c3cb/temp..dxslzkma.crash?downloadKey3=1438984413_b6f3584e263db2c6a0e387b6b725763a
I’m trying to solve my problem over the month and I have still no solution. Any idea? Thank you in advice.
We are facing issue with "iOS Push Notification" functionality with Mobile First 7.0.
We have downloaded push notification sample app from
Sample App. As MF 7.0 doesn't have any sample app. So we used sample app of MF 6.3.
After installation we have tried to "subscribe" through iOS device. Its throwing below error and app is crashing.
[ERROR ] FWLSE0020E: Ajax request exception: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. [project PushNotifications][ERROR ] FWLSE0117E: Error code: 1, error description: INTERNAL_ERROR, error message: FWLSE0069E: An internal error occurred during gadget request [project PushNotifications]The transaction has been rolled back. See the nested exceptions for details on the errors that occurred., User Identity {wl_directUpdateRealm=(name:null, loginModule:WLDirectUpdateNullLoginModule), SubscribeServlet=null, wl_authenticityRealm=null, wl_remoteDisableRealm=(name:null, loginModule:WLRemoteDisableNullLoginModule), SampleAppRealm=null, wl_antiXSRFRealm=(name:mibphsqb0hb1bfcko7t0nfstts, loginModule:WLAntiXSRFLoginModule), PushAppRealm=(name:Test1, loginModule:PushAppLoginModule), wl_deviceAutoProvisioningRealm=null, wl_deviceNoProvisioningRealm=(name:89E62244-B169-4C8E-BB83-BD7F6868310E, loginModule:WLDeviceNoProvisioningLoginModule), myserver=(name:b71e8870-df42-424a-bc38-924c645d621e, loginModule:WeakDummy), wl_anonymousUserRealm=(name:b71e8870-df42-424a-bc38-924c645d621e, loginModule:WeakDummy)}. [project PushNotifications]
com.worklight.common.log.filters.ErrorFilte
Why are you saying MFP 7.0 doesn't have any sample? it is linked to in the tutorials for MFP 7.0, here: https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-7-0/notifications/push-notifications-hybrid-applications/event-source-based-notifications/
So first try to the appropriate sample.
Additionally the error log does not reveal anything... provide logs from Xcode.
As for the crash - make sure you are using the latest MFPF 7.0 iFix from IBM Fix Central as an iOS push-related fix was delivered some time ago. You may be using a version affected by the bug.