Im having this issue today, we developed some apps years ago, with an adobe id from one of our developers. The person who own the account doesnt work with us anymore, so we are trying to migrate the account, just for the certificates we have there (apple and google) , cause i dont think we have the source files of those certificates.
Anyone had this issue in the past? Any idea how can we resolve this?
Thanks!!
This is a tricky one - I'd recommend creating a "company" Adobe account going forward so that you don't run into this again.
Beyond contacting that user for access, perhaps log a support request with Adobe.
Even with that option though, there's no way to download the keys/certs from PG Build, so your best bet is to obtain them from the source - your Apple Developer and Google Play Developer accounts.
Related
I've been developing a Swift app for a while now on my own individual developer account linked to my longstanding everyday AppleId - so the AppleId also has all my bought music, apps, appleTV and other content etc etc. As I have developed the app I have realised that it has considerable commercial potential, and so would rather release it under an organization (a private limited company) than under my own individual name.
The app itself is relatively straightforward, it is self-contained other than having a single non-consumable in app purchase. I have not yet uploaded the app to AppStoreConnect, although I have set up the app name and the in app purchase on AppStoreConnect for testing purposes. I would like to release in the quickest way possible now. Using XCode 14.
What is the quickest, most straightforward and trouble-free way to achieve my goal? Should I:
Release it under my own individual developer account and then ask apple to change my individual account to an organization account? Are there any complications with this given that this dev account is attached to my personal AppleId? How long does it usually take Apple to achieve the change? Does the App remain on sale throughout? Are there ever any problems or is there anything else I should be aware of?
OR
Set up a totally fresh AppleId and create a new developer account for the organization on this id? (I appreciate this will cost extra money but am willing to bear the cost). If I do this, how do I transfer the app from my individual account to the organization account? Do I have to go through the Apple 'transfer an app' process? Are there any pitfalls with this? When the transfer is complete, how do I alter my XCode set up to continue working on the app under the new account? Also, as I have not yet submitted the app to AppStore (although I have set up the name / IAP ) can I simply use XCode to point the app at the new account and upload it to that instead without invoking the Apple 'transfer an app' process - how would I alter my set up on XCode to achieve this?
I am currently in the process of setting up the company, and should have necessary info eg DUNS no etc fairly shortly.
While I'm familiar with development itself and I've already released one paid app on the AppStore under my own individual account attached to my everyday AppleId, this seemed to be a relatively simple and automated procedure. My main difficulties with my current problem seem to stem from the fact that I have never worked as part of a swift development team, and I understand very little around the actual 'architecture' of app development, eg XCode signing / teams / bundle ids etc, and I'm really struggling to understand the technicalities of the connection between XCode / Developer Account / AppStore Connect / AppleID.
I've looked through other posts on this topic but most seem several years out of date, and I am aware that AppStore functionality in this area has changed over the years.
Any help would be greatly appreciated - particularly if you can recommend which route to go down and answer any of my specific points. I have tried asking Apple, but all I get back are standard replies directing me to their app transfer process - unfortunately though I'm something of a solo outfit and I really need the benefit of people's experience here, as I need this process to go quickly and smoothly!
Cheers!
So I just spent all weekend debugging and building an app for my client. I don't have my 100 dollar Apple Developer License anymore, so I can't upload it. I thought my signature would just be under my client's team automatically after they added me, but I guess not.
How can I sign the app as my client's team, so they have it, and I can upload to their dashboard?
I can't seem to be able to Google the right thing to find an answer.
Oh, and secondary question; could I just get the team license under my name to sign it, so I don't have to re-achieve it again? Not a huge deal if I have to wait again, but it would save me some time.
Edit: I did also directly ask Apple's support team, but I figured I would ask this here incase a fellow dev had an answer for me. I can't be the only freelancer who's had to build and push an app for a client. Cheers!
I've experienced a few apps that have had some time on the Mac App Store, but were later removed either by Apple or the developer for whatever reason. The developer then followed up with an offer where you could register the app by downloading one from their site onto your system with the App Store version already installed, which would unlock the full features of the new download.
How does one go about verifying an authentic purchase like that? Ideally I'd prefer examples in Swift if you would be so kind, but ObjC is manageable as well.
Here are official docs about receipt validation:
https://developer.apple.com/library/archive/releasenotes/General/ValidateAppStoreReceipt/Introduction.html
There’s also WWDC 2013 video 308 called “Using Receipts to Protect Your Digital Sales”.
It’s recommended to implement your own validation code, but it’s overwhelming and error prone if you’re new to this. There are projects on GitHub that can get you started.
When developing online game I would really like to avoid supporting different protocol versions. The server can check the version of a client and deny login until the client gets updated. But the problem here is that I need the app update to become available simultanously at the same time on AppStore and Google Play.
Is it possible to do? How do you solve such versioning problems?
Well, I am not sure how it works for the GooglePlayStore but if you choose Developer Release instead of automatic then you could just release it in the moment it approves on the GooglePlayStore and about 30mins. later your iOS app will be online and available as well. That's what I'd do.
I am currently experimenting with programming for my Nokia 5800 XpressMusic (running Symbian 9.4). Setting up the development environment (Carbide C++) was already a huge pain, but now that I am actually able to build something the pain doesn't stop! It seems there is an incredible overhead involved when you actually want to test an application on the phone. But I really hope somebody more experienced than me knows some easy way to do it.
If I understood right every application has to be signed. I can sign applications myself, so this is not a problem and it seems to work fairly well. But then it seems not all capabilities are available if I do this, and the one I need is amongst them. So now I have the option to buy a publisher ID to get a developer certificate (current cost: 200$ - no thanks) or I have to upload the application every time to symbiansigned! Every time I change the code and want to test on the phone I have to upload the thing using a stupid web form!
But now I was excited to find that you can do some remote debugging stuff with a thing called TRK (maybe this spares me the signing?). I hoped that I could use this to connect Carbide and my phone. But this doesn't quite work. My phone doesn't show the application required for this connection although it installed properly. I had a look at the supported Symbian version number and it seems to be 9.2, so not mine :( Stuck again?
And the emulator is no option because it doesn't support sensors and cameras :(
So what am I doing wrong (and sure there must be something)? Is the only way to test my app on the phone to actually upload it every time, wait for it to getting signed, download it again, install it and test - just to see it didn't work and that I have to repeat this process over and over again?? PLEASE no...
follow the instructions here http://www.forum.nokia.com/Distribute/Packaging_and_signing.xhtml to get yourself a free certificate for 5 testing devices, then you can use this certificate to sign your applications directly without using open sign.
When you use TRK, your application is still installed on the phone (in background, with so called silent installation API - by the way, you can use it too, but it's offtopic), because the only eligible way for a binary to get into the phone is the Installer Service. So you still need some certificate. All three options to get certificate mentioned here are ok, though the last, free one (from Mahdi Hijazi), I suppose, is the preferred. :)
Please go to
http://www.opda.net.cn/register.php
then apply for a OPDA Developer Certificate and download signer tool from the site and use it to sign your symbian applications.