After extending BaseGameActivity on MainActivity, when you open the game it shows the animation of connecting to Google Play Games but at the end shows the message Failed to sign in. How can i solve it?
You may follow this documentation that describes how to troubleshoot issues that you might encounter while developing Android games with the Play Games SDK.
If you are unable to sign players into your game, first make sure that you have followed the instructions to create your client IDs and configure the games services.
If you still encounter sign-in errors, check the following items to make sure that your game is set up correctly.
Check your metadata tags
Check your package name
Check the certificate fingerprint
Check that test accounts are enabled
If you are using Proguard and are seeing errors on the obfuscated APK, check the target API level on your AndroidManifest.xml. Make sure to set it to 17 or above.
Here's another reference which might also help: Google Play Services fails to connect
Related
I am attempting to develop a Wear OS app which is dependent on a paired Android phone to perform some higher complexity computations. To this end I have implemented on the wearable side the proper infrastructure to pass a PutDataMapRequest message to the phone app, where I am having trouble is extending the WearableListenerService class on the phone side. When I alt+enter to see the suggested actions menu, the option to add the requisite library is there. However when I select that option nothing happens and the option is still there afterwards (the error is not rectified). I will caveat this by saying I have only been developing for Android for about 2 weeks so some of this Android Studio and its' quirks are still a little new to me. Prior to this point I had attempted various incarnations of building this app. The first where I had built the apps separately, and on that attempt this same extension caused problems (the IDE didn't even offer any suggestions at that point). I also tried loading the data layer api sample to find an example of the wearable listener service but unfortunately it is only present on the wear side of the app. The original source of this approach was from this tutorial, which I know is a little old at this point (at least one of the calls on the wear side are deprecated which I already worked around). At about 2:00 in the presenter is able to extend WearableListenerService without any issue within his phone side app and I have no idea what I am missing to be able to do that. I also did look into just trying to add the support library manually but to no avail.
Ok so, for anyone who runs into a similar issue down the road. The solution appears to be that when you create a wearable app through the new wizard and attempt to add an application module to the project, you will need to manually add the following lines to your phone app side gradle file under dependencies.
implementation 'com.google.android.gms:play-services-wearable:17.1.0'
implementation 'androidx.wear:wear:1.1.0'
This allowed the IDE to recognize the requisite classes and import them accordingly into the companion phone side application.
I have installed the Google assistant service by following the guide in the official documentation. Now, I want to add custom actions in the SDK.
Just to test, I used the same action and code they have given. But, as it runs, it just says Sorry, your app is not supported on this device . I then wandered around in the troubleshooting page to find out that this was already addressed by Google. They have mentioned just about the issues caused due to triggering surface capabilities related to the screen ON. But in my case, all the surface capabilities are turned OFF. But, I'm still facing the same issue. Can anyone please help..?
I am a developer which working on security related area.Recently I
met a little problem. If I got a app such as android .apk or IOS .ipa.
How can I check whether it has malicious actions?
The first thought came to my mind is to check its manifest. To see
which kind of permission it has requested. But this general method can
not detect some actions such as record the screen snapshot or record
user tap position on screen.
Then I switched to search how app store and google play check the
app which submitted by developers. Turns out that they first check the
certificate or signature of the app to make sure it has been published
by trusted organization. Then statically check the system permission
that the app requested.
I guess there must be some in-depth detection method or theory
which used by google and apple to make sure their app is safe to
download. Can anyone provide me some useful information or website
link that I can learn from?
Thank you.
I followed https://developers.google.com/actions/dialogflow/first-app tutorial and built my first google action. The action is working fine on my laptop browser in the test (Followed "Preview the App" section of the tutorial) environment. However, when I am trying to use this action on my phone by saying "OK Google talk to my first app". It's not working. Is it supposed to work on my phone as well? I have logged in with the same Gmail account on my phone also.
PS - I have posted the same question on "actions on google" google plus community google as well but I am not sure if that community is to post such questions or not. Therefore, I am posting it here also.
Thanks in advance!
Once you have enabled testing through the simulator, it should be available on all devices (mobile, speakers like Google Home, etc) with the same account your simulator is running in. Double check to make sure they're the same account.
In your case, however, you may be using the wrong invocation phrase. If you actually said what you did above, you need to say the exact same thing that you typed to invoke it.
If you haven't set a name in the configuration, then that phrase will be
Talk to my test app
Update
As you note in the comments - you also need to make sure you're running the Google Assistant, and not one of the other voice search components. The Google Assistant requires:
Android 6.0 or higher
Google app 6.13 or higher
Google Play services
1.5 GB of memory
720p screen resolution
Phone set to a supported language
As you probably already know you have to enable Web & App Activity, Device Information, Voice & Audio Activity in the Activity controls page.
Then you also have to be sure that the language of your agent is the same used by your google assistant.
I solved thanks this last step.
Hope this helps
So assuming you've already launched media on the receiver from an iOS/Android/Web app, how can another web app join this activity and control the media? I noticed that the cast API has a 'JOIN_ACTIVITY' in it, but there's nothing that currently uses it. Nor do you know the activity's ID to join it..
This is similar to How to check if a ChromeCast Session is already in progress however, this answer does not help to connect to an existing application
However, using the javascript API, even if you know your app is running I can't find a way to connect to it without re-launching
I managed to get some answers from the Google engineering team:
We allow clients to reconnect to the same session if they are launched
from the same origin (i.e. http://www.somedomain.com:80/). We don't
have the support in the V1 protocol stack to implement this across
multiple browsers. We can hard code something for V1 like mapping
origins to app ids, but it will still be some eng effort to add the
API support as well.
In short, the functionality from Android and iOS is currently missing from the Chrome SDK... hope it comes out soon.
EDIT: To update this, now that the official public SDK has been released, this is now supported!