We used to be able to get the title, subtitle, and body of notifications in Notification Center using the solution here.
Running that code now produces the error:
script error: A “text” can’t go after this identifier. (-2740)
Is there a new way to do this in Ventura?
Related
I am quite new to Appium testing and I am trying to use Appium inspector https://github.com/appium/appium-inspector.
I run my app 'IntegrationApp' on iOS simulator in Xcode. The bundle identifier shown in Xcode for 'IntegrationApp' is 'com.facebook.IntegrationApp'
And 'IntegrationApp' is running successfully on simulator
Then when I try to connect Appium inspector to app 'IntegrationApp' on simulator, it gives error 'Failed to create session. An unknown server-side error occurred while processing the command. Original error: App with bundle identifier 'com.facebook.IntegrationApp' unknown'
What might the issue be?
Incidentally, the app comes from Appium installation and the 'WebDriverAgent.xcodeproj' project is under .../node_modules/appium/node_modules/appium-webdriveragent, so I assume it's a normal app to use for simulator, i.e. no need of signing etc.
I also tried other app that should already exist on simulator, like app store, but it's giving the same error.
I can't tell you what exactly is the issue but this app is not meant to be used like this. If you just want to get familiar I would advise you to use any of the native iOS apps - like Settings, Camera or whatever. You can find their bundle IDs here
I'm preparing an app for the Mac OS app store. The app is a package that consists of a precompiled binary and a bunch of configuration parameters embedded in it's info.plist. The app isn't under development - it's been in use for several years, but I'm planning
to smooth the distribution by getting it into the app store.
I created a .pkg for the app using "productbuild", and the package installs fine.
My problem is that feeding the .pkg to the transporter app always fails with
"failed to create the .itmsp for .pkg Failed to get the apps bundle id"
the info.plist looks fine to me.
Q: what's wrong, what can I do about it, or is there an alternative path into the
app store.
This error seems to occur for many different reasons. In my case, my Info.plist had an empty value for the NSHumanReadableCopyright key and it was missing the LSMinimumSystemVersion key entirely. After adding both of those, and resubmitting, the error no longer occurs.
So my best advice for combatting this error message is to compare your Info.plist to a known good one and see if you are missing any keys or if any of the key values are empty or possibly invalid. Unfortunate that this error message is a red herring.
If you use xcrun altool --validate-app to attempt to upload your app rather than Transport, it will give you the reason why it is failing to upload. In my case, Transporter gave me the same vague error message you were getting. At first, I tried adding LSMinimumSystemVersion, but still failed with same vague error. Then I tried xcrun altool --validate-app, I get:
2021-03-29 00:35:11.876 altool[1291:17262] *** Error: Unable to validate archive 'myApp.pkg'.
2021-03-29 00:35:11.876 altool[1291:17262] *** Error: code -27002 (Unable to validate your application. The Info.plist in the package must contain the CFBundleShortVersionString key.)
After I then added CFBundleShortVersionString, I was moving on.
I assume you already made all steps needed before submitting your Mac App. So then the easiest way to send it to the Apple Store Connect is generating an Archive and using Organizer.
Open Xcode
Go to Product -> Archive
Wait until an Mac App Archive is generated
Go to Window -> Organizer
Select the version of your app that you want to submit and then click on Validate App
If everything is ok, proceed clicking on the button Upload App
Finally go to the Apple Store Connect and just publish it
I am using xamarin.forms to do an app for ios and Android.
I am using Rg.popup as well.
The problem is: when I run the app in ios and before my rg.popup appear the system shows a system popup, my layout is strange...
How it can be
does Someone know how to solve?
Remote notification is not supported on Simulator, so system log an error about this and your code shows it with an alert. You need a real device to test remote notification.
To get rid of the alert view, find the code which shows the system alert in FailedToRegisterForRemoteNotifications method in AppDelegate.cs. Forbid it when the error code is 3010(which is for the error).
I'm working on the iOS 10 APNs function, trying to add Notification Service Extension to an existing App, add the function of pushing an image to the App.
After the extension was added, it did receive the pushed message. But couldn't receive the image, the function(wrote in the extension) of downloading the pushed image didn't execute during debugging. I checked the content in the App package, confirmed that the extension was installed in the App, it just didn't work.
What made me confused was that: I built a new testing project with same bundle id. The testing app could receive the pushed message and show the image correctly.(please see below screen shot)
What's wrong with the existing project? I tried to find the difference between the existing project and the testing project, yet found nothing in the code, setting, environment.
Does anyone encountered this before? I have been struggling in this for a week...
reference:
WWDC 2016 APNS Guide: https://willowtreeapps.com/ideas/wwdc-2016-rich-notifications-in-ios-10
Apple notification guide:https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/ModifyingNotifications.html#//apple_ref/doc/uid/TP40008194-CH16-SW1
Finally this bug was fixed, please see the attached image. XCode recommends setting the architecture as automatic and I did so, then the notification service extension worked and could receive the pushed image. I don't know why this setting caused the problem, but I'm sure it works.
I am working on a app written in Swift for Mac. I am using XCode 6.4 on OSX 10.10.4
I recently noticed some weird messages regarding in app purchases.
Initially when I run the app the method request:didFailWithError of SKProductsRequestDelegate is invoked as seen below
func request(request: SKRequest!, didFailWithError error: NSError!) {
println("Failed: \(error.localizedDescription)")
}
This code snippet prints Failed: No bag entry
Further, to solve this I cleaned the project to remove the old binary.
When I try to execute the newly build binary from finder it says
After clicking on Sign In nothing happens.
Questions
What exactly is No bag Entry?
Why is the alert (present in image) saying that I have already purchased the app, although I am testing in App Store Sandbox?
Note
The reason I am executing the App from Finder(outside Xcode) is that Mac applications are required to be executed outside Xcode for first time, so that it can fetch the Receipt from Apple Server
Mac App store is kept logged out through the entire process
This error popped up with out any reason. I am pretty much sure that something has to be done outside Xcode.
Update
Apple has updated the Technical note TN2206 on July 27 and the change is titled
Cover changes to linking to dynamic libraries outside of an app bundle.
I have dynamically linked openssl library in my app, I guess it has something to do with it.
I've seen the "No bag entry" error passed to my -request:didFailWithError: method in my SKProductsRequestDelegate twice so far whilst developing and testing my Mac app.
The full NSError I've seen is:
Error Domain=ISErrorDomain
Code=3 "No bag entry"
UserInfo={
NSLocalizedDescription=No bag entry,
NSLocalizedFailureReason=Could not find key 'p2-product-offers' in bag.
}
I don't know what p2-product-offers is: this isn't a string I'm using in my app.
From searching the web, it seems that ISErrorDomain is something to do with StoreKit.
Both times I've seen this, my Internet connection has been a bit flakey. My current guess is that this error means "the Internet connection dropped whilst StoreKit was retrieving the product information".