I have old BB signing files from last year. Would I need to update these for BB10? I can't get my app signed. I keep getting invalid password, but if I delete these, it asks for the author.p12 back. And I know my password. Let me know.
You have to ask for new keys: https://www.blackberry.com/SignedKeys/
Related
I'm working on a large app. In the middle of development we decided to add push notifications. I created a new App ID in the Apple Developer Site.
The App ID is: 8NG823UBLP.com.mobiikk.ServicioDeAdministracionTributaria
Push is enabled for Production and Development.
Certificates were downloaded for both and the .p12 created too.
.p12 files are on the server and everything looks good on server side but the app is not receiving push notifications.
The app is granted push notifications and they are set to ON in settings.
The bundle ID was changed to com.mobiikk.ServicioDeAdministracionTributaria in the info.plist
The team has been looking for an answer for this without any luck. Help will be very much appreciated.
If you switch on notifications for existing app, you'll have to recreate the provisioning profile (better clear old profiles from Xcode organizer and then refresh them or shut down xcode and replace them via iphone configuration utility - be sure to get rid of older provisioning profiles)(you can still keep the same old appID, just refresh that AdHoc/Enterprise/AppStore profile - it contains note about being APNS-enabled)
Otherwise your serverside may look great, but app will never get successful notification of registering your device and could not pass token to your server side ,
but you would get failure notifications warning you about wrong entitlements and missing APNS profile in device console log
As you did not state what are you doing in the app side it's hard to tell where is your problem exactly.
Just in case someone has the same problem. The only way around this was to create a brand new project. I copied every file in the old one to the new one. Gave it a new Bundle ID, created a new provisioning profile, new App ID, and downloaded new certificates. So in summary, there was no easy way to transfer an existing project to one that accepted push notifications.
I've just accidentially submitted an update for my app via organizer -> distribute, not noticing that my build settings still had the developer certificate set instead of the distribution certificate.
will the update still work on the users devices, or will it fail to install? I did not find any option to reset the submitted app, so I will probably have to wait until its published. Or will it even be rejected for not beeing signed with a distribution certificate?
App Store will likely reject if you have the wrong certificate. Send Connect an email and explain, they're usually pretty helpful.
I'm going to update an iphone app but I cannot Testing it on the itunes portal.
I made the update in itunes portal, I build it, and When I want to validate it, it doesn't runing because of certificate so I'm asking if I don't have to make a new certificate?
When I use the certificate that I used for the first submission:
Application failed codesign verification. The signature was invalid, or ti was signed with an Apple submission certificate.
The status of the certificate on the Portal is Active.
I put All the line of "Code signing" to iPhone Distribution and edit scheme>Archive>Release :
printscreen.
I re-sign the app with the same certificate when I try to validate it on iTunes...
Thanks to help me
EDIT : I make that but I still have the same problem:
Download certificate
Import it and deletete old one
set the new certificate overall ^^
Get the error xD
Please help me I need to do that before monday
If your old certificate has expired you need to create a new one to be able to update your app.
Are you using the certificate on the computer that generated it in the first place? If not, your public key doesn't match and you'll have to request a new one even if the current one hasn't expired.
It looks as if your code signing build settings are automatically detecting which certificate/profile to use. The image is cut off so I can't see what certificate/profile combo is being used, but it sounds as if it is selecting your Ad-Hoc combo and not your App Store combo. Try changing the code signing build settings for the target(s) you are using to build for the App Store manually to your App Store profile. If this makes no difference, can you please show the rest of your code signing settings (not chopped off on the right)?
I followed indications to make Ad-Hoc on the official portal : http://developer.apple.com/ios/manage/distribution/index.action. It says that we have to make a new entry on entitlements (get-task-allow at true) and I didn't delete the row in the entitlements file!!
Now all sounds OK, sumbitted !
I create iTunes connect test user, but when I am trying to test in-app-purchase, my app in iOS simulator says, that i need to verify my apple id. How can I do it?
Text of error view:
You haven't verified your apple id.
Tap OK to see instructions.
When I taps OK, it hides alert view and it is end.
This has been happening to quite a lot of people in the last couple days and there is a thread in the Apple Dev Forums: https://devforums.apple.com/thread/128982?tstart=0
No need to verify it,
Actually its a dummy account for testing purpose. So, if you enter dummy email id which is not exist will be fine. And if you try to enter real email id, then it send you verification mail. But don't worry if you're not verify that that will work fine.
But better you should apply dummy email id instead your real email id to avoid this confusion...!?!
It's some times happens. But you can test in-app purchase with test user.
Just make sure below points:
1) You test the app in device (not simulator).
2) Before test the in-purchase, you should be logged out from app store on device.
Cheers.
I just ran into this issue and it seems there is a simple way to rectify the issue.
Issue:
After creating an Apple ID(best to use a fake email that doesn't exist to reduce headache) for a test user account in Albania, I signed out of the normal Apple ID I use from within "Settings>iTunes & App Stores" and leave it signed out.
Then I start the app I'm testing, attempt to purchase anything within the app, at which point I'm prompted with a message that asks to use existing Apple ID or Create New Apple ID.
I choose the Use Existing Apple ID option.
Then I'm prompted to enter email & password.
This is where you enter the test user account info you've created in iTunes Connect.
After entering the test user account info, a message saying that this profile/account has not been verified/used on this market previously, then I tap "OK", and it redirects me to the App Store.
At this point do not do anything further within the app store or the prompts that appear within it, it will just create further confusion/problems
Instead, back out of the store, and re-open the app your testing. At this point, try to purchase that same item again and it should work just fine.
I have no idea why it redirects you to the app store to begin with, but for whatever reason it does. It does seems strange that in-app purchase testing would ever re-direct you to the store, but it just does, so try to ignore the idiocy and move on. Just pretend it didn't happen, and go back into your app as if nothing happened and everything makes sense.
Hope this helps
We all have to file bug report to Apple so that it gets addressed faster. AFAIK Apple does not really care about discussions in their devforums.
And yes, I started experiencing the very same problem since Oct 21.
I found problem. Now we must use our real email and they will send email to verify it.
I have downloaded a provisioning profile from my id, but when I drag into Xcode, and then in the provisioning profile section it says
a valid signing identity matching this profile could not found in key chain
I am trying to download the existing profile and drag into Xcode, but this gives me the problem that how could I deploy my application to the device?
Delete all your private and public keys. Create one new one by using the assistant to request a certificate...
Before you do anything else name the key by double clicking on it and typign a name that identifies it as the one key you will keep.
Delete all others.
See this question which you might have found with a quick search, from earlier today.
For the error:
Valid signing identity not found
see Apple's published steps to resolve this problem.
I had the same problem yesterday and solved it successfully. It took me almost a week to figure out the process.
I think your keychain does not possess a valid developer certificate or Apple WWDRCa certificate. To solve this download your developer certificate and drop it into your keychain. Then download the Apple WWDRCA certificate and again drop it into your keychain.
Remember that you must have your private key along with your developer certificate. By now, your keychain will have a matching profile. Now drop your provisioning profile in your Xcode and see. It should work.
I faced the same problem yesterday.For some reason i deleted my keys,because of that my provisioning profiles were with warning "valid signing identity not found".
As i worked on push notification previously i have saved "X.p12"file from private key .if u saved that then u have to double click on that and give that password that u given while saving it. that's it my provision profiles are valid now :).