I have successfully tested an azure apns hub in sandbox mode. Now when I try to switch over to production, nothing works. I have read the tutorials, and i'm sure that I generated the production certificate right. Does anybody have an idea what the problem would be? At some point I think I have read that while I was using an Iphone to test the sandbox apns, it may not work after switching to production.
After debugging some more, I figured out what the problem was. I had to run my application with the production certificate. That means, that I could not test the production APNS running the app through Xcode, since xcode would automatically install the development certicicate that is linked to the sandbox apns. Run the app outside of xcode, with the production certificate.
Related
This is a question that has been asked several times, but no solution has worked for me.
I finished coding a Xamarin Forms app and now, I want to release it. I signed the app with a new certificate and an Adhoc provisioning profile. Everything signs well.
But when I distribute the IPA, after installing the app, iOS shows this message:
"This app cannot be installed becaue its integrity could not be
verified"
I chosed Ad-hoc as provisioning profile config.
This app has the same namespace and bundle id as its preceding app found in the app store already. I built a new version, within a new solution and created certificates with the same bundle id.
The device on which I am trying to install it is an iPhone XR, that I use to test the live version of the app and the one in development. When I run the app in debug on the phone, nothing wrong happens. But signing and distributing causes the app to not run.
After several hours of debugging, I found out that my bundle display name for the new version of the app was written in lower case, whereas the bundle display name of the former app was camel case. When I changed the new app's bundle display name to camel case too, everything went smoothly.
This is so weird.
I hope its okay to ask here, I could not find a specific existing thread for this.
I have developed a Blazor server application in .NET 5 for a client, and it has been hosted on azure app service (on Linux plan). We have several environments (Dev, test,prod), and the deployed app works as intended in all environments, except when deployed to the production app. It works fine for a while, but at a point something happens and the browser dev tools console says 404 not found for all the css and script files. Because it is .NET 5, application insights are not supported in Azure.
In the Program.cs's CreateHostBuilder I have added the UseStaticWebAssets, and in Configuration in Startup.cs app.UseStaticFiles.
And as mentioned, it works perfect in all other environments, and for a while it works good in production after restarting the App Service.
Any idea what might be causing this?
Thanks!
Morten
I used this code to build my app.. Actually it's working very fine on loose build but not on testflight build.. It would be great if anyone knows this?
Mistakenly I was using the sandbox certificate, replaced it with the production certificate and it works.
How can a deployed cloud service application be debugged?
I am trying to render a RDLC report in my application using Topics & Subscriptions.
Whenever I run the cloud app locally, I don't receive any errors. But as soon as I deploy it over the cloud, I get an error which aren't described up to an extent so that it can be rectified.
I found that the error comes when the report is ready to be rendered and not anywhere else.
I am looking for a possible mechanisms (inserting breakpoints like we do locally, etc.) using which it is possible to debug a deployed cloud app.
Since I am using VS2012 Express & professional, intellitrace does not work here.
You need to enable Remote Debugging for your Role, and you will be able to debug your code in the cloud with any type of Visual Studio.
I don't think you can, however Intellitrace was build for that purpose. You enable Intellitrace in your cloud instances, and then you can "playback" that instance locally, thus debugging and spotting the exceptions thrown.
Here's MSDN's article on that
http://msdn.microsoft.com/en-us/library/vstudio/dd264915.aspx
Having Intellitrace only in the most expensive version of Visual Studio makes developing for Azure far more expensive than it is advertised at. There are some situations, such as when a role is starting up, that you pretty much can't do anything without Intellitrace. If you find that you are in one of those edge cases 'evaluate' VS ultimate in a local virtual machine. You may need to re-evaluate at some point in the future, in which case you will need another VM.
I am working with my first iphone app. and now i am working with push notifications. i am using urban airship for push notifications. in developement phase everything was working fine. device tokens were registered and then i could send push notifications from urban airship. but its not working with production phase. i put my app on app store but push notifications didnt work. i tried to search alot on urban airship to solve this problem but couldn't. I think there is something i have to change when i make binary file for that app. can anyone help me with this? any tutorial which will help me. Its working fine in development phase but not working in production phase. Thanks in advance.
I had the same issue at my company a couple months back.
There are two sets of urbanairship credentials (by credentials I mean: Application Key, Application Secret, Application Master Secret) sandbox and production. When you were developing the product, you were using the development credentials and everything worked great. Those will not work after you release the application to the AppStore due to the way urbanairship works with Apple's Notification sandbox etc etc.
Track down the production credentials on urbanairship and change them out in your source code before resubmitting and you should be all set. You'll need to do an adhoc build to verify (I believe). Good luck!
Documentation on Development/Production settings: http://urbanairship.com/docs/push_index.html#development-or-production