Trying to run Watchkit - Notification. Receiving the following error:
Error launching 'Watchkit extension" - SPErrorUnknownMessage
Has anybody else come across this error before or knows what it means? Haven't been able to find anything online about it.
Cheers,
A
I have seen this issue and it was related to an error in the structure of my .apns file - there was a comma missing in the json. Once this was corrected, notifications worked again.
Try looking for errors in the Payload apns file that you are using for this target.
I got this message when I removed the file PushNotificationPayload.apns from the WatchKit Extension in Xcode.
Take a look into the Run-Section the Schema: If the Watch Interface entry shows something like Dynamic/Static Notification, it will likely expect some apns-file as notification payload. If that file is missing (or faulty as for Gavin Potts), you'll get that error.
So either fix the apns file, or change the Watch Interface entry to Main or sth. else.
This error occurs due to PushNotificationPayload.apns. Sometime closing quote may be missing.
Related
I have the following issue when I upload my React Native app to the app store
The app references non-public selectors in Payload/AppGeolocNative.app/AppGeolocNative: getAuthorizationStatus:, isPassthrough, newSocketQueueForConnectionFromAddress:onSocket:, onSuccess:, relativeSize, removeValuesForKeys:completion:, socket:didAcceptNewSocket:, socket:didConnectToHost:port:, socket:didConnectToUrl:, socket:didReadData:withTag:, socket:didReadPartialDataOfLength:tag:, socket:didReceiveTrust:completionHandler:, socket:didWriteDataWithTag:, socket:didWritePartialDataOfLength:tag:, socket:shouldTimeoutReadWithTag:elapsed:bytesDone:, socket:shouldTimeoutWriteWithTag:elapsed:bytesDone:, socketDidCloseReadStream:, socketDidDisconnect:withError:, socketDidSecure:, spanArray, spanArray_Count, strikeThrough, underline
I do not really understand what is the issue, everything is working ok, this is just a warning
I had the same problem and I got an email from Apple and it was telling me the reason for the error. The problem was some information I needed to add to the info.plist file. In my case it was the NSPhotoLibraryUsageDescription.
Check if you have any email from apple which telling you what is missing.
In the last couple of days we were getting some bug reports due to our Push Notification Feature not working anymore.
We use React Native with react-native-notifications (newest version). The build we have up in the app store is from the beginning of October and has worked just fine.
Now, out of nowhere when i press the button that is linked to requesting the PushToken, nothing happens - not even the Failure-Callback is triggered.
When i open the device console i just get these two errors when i click the button:
error 14:11:19.891971+0100 SpringBoard Entitlment 'com.apple.private.usernotifications.bundle-identifiers' for online.*.* required to request user notifications
error 14:11:19.892050+0100 SpringBoard [online.*.*] Requesting authorization failed because of missing entitlement
But obviously the entitlement for Push Notifications is set (and always has been).
Any of you got any ideas what to check? I'm a bit clueless right now.
Best!
Just a quick heads-up. Problem was, that my Product Name (Target -> Your App -> Build Settings -> Packaging -> Product Name) had german special characters.
See also: https://developer.apple.com/forums/thread/660648
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'm trying to get QLPreviewController to display a pdf document. When the document is saved to the device the file location string (within the documents folder) is recorded. I later create a URL from that file location string with URL (fileURLWithPath: location) and use that as input for a QLPreviewController data source. Up until now, that worked and the quick look would present with the document properly.
Unfortunately, that no longer works. I updated to Xcode 11 (swift 5.1) this morning, and now my QLPreview controller doesn't show the document. It still presents, but with a gray background that says "Document name" and "pdf document." If I click the share button and go to print it, the print preview correctly shows my file (and pushing print does print the correct file in its entirety) so I know the file is there, and is readable. It just won't display in the QLPreviewController for some reason. (This error is also reported on the apple developer forums, but nobody there had any suggestions to fix it other than trying on a non-simulator device which I've already done.)
The debug text from Xcode is as follows:
Could not create FPSandboxingURLWrapper with url: file:///Users/username/Library/Developer/CoreSimulator/Devices/F69CC8ED-C164-4E36-946F-E675C7FC7365/data/Containers/Data/Application/739F1371-1A79-41B1-8FF5-E8ACC0FEA976/Documents/mydoc.pdf, error: Error Domain=NSPOSIXErrorDomain Code=22 "couldn't issue sandbox extension com.apple.app-sandbox.read for '/Users/username/Library/Developer/CoreSimulator/Devices/F69CC8ED-C164-4E36-946F-E675C7FC7365/data/Containers/Data/Application/739F1371-1A79-41B1-8FF5-E8ACC0FEA976/Documents/mydoc.pdf': Invalid argument" UserInfo={NSDescription=couldn't issue sandbox extension com.apple.app-sandbox.read for '/Users/username/Library/Developer/CoreSimulator/Devices/F69CC8ED-C164-4E36-946F-E675C7FC7365/data/Containers/Data/Application/739F1371-1A79-41B1-8FF5-E8ACC0FEA976/Documents/mydoc.pdf': Invalid argument}
Something else that might be of note: I was getting similar error messages before in a previous iteration of my code, and I figured out the problem was that I was passing a url from string instead of a fileurlfrompath, and changing to that fixed my problem. I suspect this is just a different problem, but the error messages were similar so I thought id mention it. Any suggestions would be greatly appreciated.
I am uploading my iOS application on app store and it is having some warning when i upload the app. warning is the app references non-public selectors in payload/appname.app/appname: _terminateWithStatus I am using facebook sdk"facebook-ios-sdk-3.8" and parse sdk "parse-library-1.2.18". can anybody guide me what should i do to remove this warning?
You can't remove this warning. You may get this warning just for using a selector in your own code or third party code(may be because of facebook sdk) that has the same name as some selector that is marked as non-public. Happens to me all the time. Never got rejected for it. So you won't worry about this warning. See this Ref. , Ref2
And also see this stack question to avoid rejection, find and remove unwanted framework.
First time i got this error and then app was uploaded but with warnings but when i submitted the second version of the app at that time Apple didn't let me upload the app and was giving me error repeatedly "Your app contains non-public API usage. Please review the error, correct them and resubmit your app" after that i found my solution in this question Finding Private API Call _terminateWithStatus Answer was not very useful for me but solution in question was very useful for me. I just removed the GHUnitIOS.framework and it worked for me. May be this info can help someone else