When I want to test my Google Play Games integration I build the app in Unity with my keystore, than upload to Google Play internal test track, than download it from internal test to my device.
When I take a look in Play Console > App > Play Games Services > Play Games Services configuration > I can see one Credential.
On Google Cloud I can see this one Credential is listed under OAuth 2.0 Client IDs and in the SHA-1 certificate fingerprint field it has the SHA-1 certificate fingerprint which is listed in Play Console > App > Setup > App integrity > App signing > App signing key certificate.
Is it possible to create a new Credential on Google Cloud under OAuth 2.0 Client IDs with the Upload key certificate SHA-1 certificate fingerprint from Play Console and than add this new Credential also to the Play Games Services configuration?
Related
Server is setup so the client providing certificate is optional. It is needed only for 2 endpoints (so small percentage).
We have noticed that users with Android 9 and chrome have complained that visiting even just a root page it asks them to provide certificate.
"The Chrome app has requested a certificate. Choosing a certificate will let the app use this identity with servers now and in the future. The app has identified the requesting server as myserverulr.domain, but you should only give the app access to the certificate if you trust the app"
Spring boot
application.properties
server.ssl.client-auth=want
This happens with very few users but it's still a problem. Is there any workaround for it?
I have 3 apps in Appstore with different production certificate, Is there any possibility to have those three apps with single production cerlificatae.
To clarify on the previous answer, you can sign all your app store apps with a single iOS Distribution certificate. You will need to create 3 separate Distribution provisioning profiles, all tied to the same certificate, but each assigned to the Application ID for their specific app. If you have an existing app store distribution certificate, you can simply use it when creating your new provisioning profiles - simply check the box next to your certificate when you create or edit the profile.
So you will have one cert (e.g. App Store Cert), and three profiles like this:
App One:
App One Provisioning Profile (App Store Distribution)
Cert: App Store Cert
App Id: com.example.appOne
App Two:
App Two Provisioning Profile (App Store Distribution)
Cert: App Store Cert
App Id: com.example.appTwo
App Three
App Three Provisioning Profile (App Store Distribution)
Cert: App Store Cert
App Id: com.example.appThree
Unless something has changed, I do not believe Apple will even allow you to have more than 2 active Distribution certificates at any given time. They allow two only so that you can create a second when your current cert is about to expire. This gives you time to ensure all your developer have the new cert prior to the old expiring, but the old will still work in the transition.
You need to have different profiles for each application. Else certificate does not matter in terms of number i.e., you can have same certificate for multiple apps only catch is you need to have different provisioning profiles for each application.
I have an app in the App Store with APNS.
Now, my distribution profile is broken and I can't add my device to the distribution profile. It is a generated profile by apple with the prefix XC:.
So one solution is to create a new distribution profile for a new version of my app and submit it to the App Store.
But do I then also need to create a new APNS certificate? Or will this also work with the new distribution profile?
Perhaps my actual question is: is there a relationship between the distribution profile and the APNS certificate? Or is it the app ID that is important to let the APNS work?
As outlined in the push notification guide, the SSL certificate used for push notifications is independent from the distribution provisioning profile used by your app.
However, you need to ensure that your new provisioning profile provides the correct entitlements for using push notifications and their production/development environment, as described here. Good luck.
My application work fine on every device for APNs notification on plug-in using development provisioning profile. When i change to ad-hoc provisioning and upload to testflightapp.com to send to tester for testing, just my own device can registered APNs device token using ad-hoc provisioning profile but the rest of the device cannot register APNs device token. How should i check on this? Any idea?
I have created HTTPS endpoint for my Cloud application (using Self signed certificate). One of the requirements of my application is requirement of Client Certificate. When i run my application i do not see a list of Client Certificates to choose from.
Does anyone have any idea on what Client Certificates are required & how they can be created?