After setting up a new independent WatchOS6 app, which now supports push notifications, getting the device to request the user for push notifications and capturing the push token. I can’t get my server to send a push notification.
With all the correct credentials and P8 set up on my NodeJS server, I have tried to push messages to the device... This is the error all the time:
Status 400 - DeviceTokenNotForTopic - Which according to Apple’s documentation, means that the Topic (BundleId of the app) is wrong. But in this case it is not.
Tried 2 different NPM packages (for elimination)
https://www.npmjs.com/package/node-pushnotifications
https://www.npmjs.com/package/apn
Both providing me with the same issue.
Has anyone successfully managed to complete a Independent WatchOS app with APNs? What am I missing
———
Update
To test the node service, a further 2 tests have been made:
Created a new app, iOS this time, with the same Bundle Identifier, using the pushToken and sending a message the service was successful
Created a new app, another watchOS, with a different Bundle Identifier, this was again rejected but the APNs for the same DeviceTokenNotForTopic issue.
To test production, the only way current is to submit to the store for App Store review. TestFlight option is currently not available for the Watch and there is no way to install a production ad-hoc .ipa manually. Once it is in the store I will continue with further tests.
Problem has been solved.
Xcode has a couple of issues, if you rely on Xcode to sort out your certificates in the developer portal then please don't.
I have been in touch with support and after a few days back and forth with logs it has been made aware that:
Apple's documentation for Independent WatchOS applications does not state anywhere that the topic (which is the bundle id) should be the one ending in .watchkitapp
Xcode does not allow you to add the Push Notification Capability to the .watchkitapp thus meaning it never creates the AppId in your developer portal.
The solution to the problem, I had, was to manually go to the developer portal and add the .watchkitapp AppId and create the certificates, thus allowing my p8 certificate on the server to allow pushes to that particular application.
I use the token based Authentication to send apns notifications.
Finally I found that I forgot to change the value of apns-topic header to watch appid.(form com.xxx to com.xxx.watchkitapp).
Hope this answer can helper others.
Related
I'm have built an app that the user save package tracking numbers and then when tapping on them the app sends a request to the parcel provider and gets back the tracking info. Pretty simple.
What i want to do is to create a backend server that stores the user's tracking codes and checks them at regular intervals. When the status change then the user gets a push notification.
My thought is to use a Nodes.js server with a MongoDB database but i'm stuck how to implement the tracking code monitoring on the server. Should i use a timer? Is there a better/simpler approach for this?
I'm trying to use the OpenProject's webhook to send workpackage's data to a third-party system, but it isn't even fired.
I did all my tests using this OP docker container from version 7.4.0 to 7.4.7 but none of them worked. In all of these images, the webhook is included and configured, then theoretically any additional setting isn't needed (except the webhook register in the web interface).
The passenger and the worker:jobs are running. There isn't clue in the log files. The webhook is enabled and set to trigger a http POST call in a localhost address.
Did anyone pass through a similar issue? I'm not a Ruby developer, and I wonder if some kind of daemon or service start is missing.
Our team figured out how to make the webhooks works. It's only needed check the Work package added and Work package updated options in the Email notifications group on System settings of the instance.
This is a undocumented setting, and I see it as a feature issue.
Nevertheless, it's working.
I have added Azure Application Insights to a number of my .Net WebAPI applications. I've noticed that I do not receive successful request telemetry from these applications. I do receive dependency telemetry and failed requests but not the actual telemetry that the request has been made. By fudging the URL or the request and forcing a failure, I can see that get sent to AI, so my issue is definitely not with the instrumentation key.
I initialize the instrumentation key as follows:
Microsoft.ApplicationInsights.Extensibility.TelemetryConfiguration.Active.InstrumentationKey =
ConfigurationManager.AppSettings["ApplicationInsightsKey"];
I have attempted to remove AI from the application entirely and added it again using the Configure Application Insights option but it still does not work. There is another of my web apps that uses AI that was configured a while back and it works perfectly, I have replaced the set up of the broken app with that of the working app and also made the package versions line up but I still only get telemetry for failed requests. The capture below from the Live Stream shows this, the red arrow points to the dependency calls made for the successful request, yet nothing shows in the Request Rate graph for it. In contrast there is a failure before it, and that is logged.
I just found the answer for this in a solved issue on the Application Insights Github. The solution is to open your ApplicationInsights.config and scroll to the telemetry module Microsoft.ApplicationInsights.Web.RequestTrackingTelemetryModule below it comment out the line System.Web.Handlers.TransferRequestHandler
This issue has been fixed and is due to go out in version 2.5 of the packages. You can read through the issue here https://github.com/Microsoft/ApplicationInsights-dotnet-server/issues/175
Try below one, it works for me:
Microsoft.ApplicationInsights.Extensibility.TelemetryConfiguration configuration = Microsoft.ApplicationInsights.Extensibility.TelemetryConfiguration.CreateDefault();
configuration.InstrumentationKey = System.Web.Configuration.WebConfigurationManager.AppSettings["InstrumentationKey"];
I am supporting a web app that uses the DocuSign Connect API to handle signature processing. We are running in production and demo environments (our production environment is using the DocuSign production environment; our demo envrionment is using the DocuSign demo environment).
The interface between my app and DocuSign Connect has been working smoothly for over a year. Sometime in the last week or so, the demo environment began misbehaving. In that time, the production environment has continued to work fine.
The problem is this:
In demo, when a signature event occurs, DocuSign is unable to call our callbackUrl. The failure log indicates the following:
https://[mywebsite]/SignedDocument/DocuSignSignatureEvent :: Error - The request was aborted: Could not create SSL/TLS secure channel.
When I look at my DocuSign Connect Settings, I see a new setting -- "Require Mutual TLS" -- that does not exist in production. I'm not sure if this is related -- I have no idea when this setting was added to the demo environment.
Even though this is a demo app, it poses a problem for us (because our demos no longer completely work). But it poses a much bigger problem if/when this same thing (via a code push or something else) begins happening in production.
Again, this interface has been working fine. Nothing has changed on my web app since the last successful callback occurred (roughly a week ago).
Please try this again, DocuSign Support indicates this should be resolved now.
We've been getting the same error starting today. Nothing has changed recently on our side to affect the demo environment. I'm thinking this might be an issue on DocuSign's end.
II've been working on adding in-app purchases and was able to create and test in-app purchases using Store Kit.
Now I am unable to successfully complete any transactions and instead am getting only transactions with transactionState SKPaymentTransactionStateFailed.
The transaction.error.code is -1001 and the transaction.error.localizedDescription is "Cannot connect to iTunes Store"!
I have tried removing all products from iTunesConnect, and rebuilt them using different identifiers but that did not help. I have also tried using the App Store app to really connect to the real App Store and download some apps so I do have connectivity. Finally, I have visited the Settings:Store app to make sure I am signed out of my normal app store account.
you probably solved it by now but for others,
sometimes it takes time for apple to process new in app purchases. this is what the message -1001 actually saying
so, cross your fingers and wait for 24-48hours, dont change anything and you will probably be fine,
it will automatically start to work when they finish processing what is needed.