I am using the flutter health package. It is working fine on iOS but on Android, it kept saying "Authorization is not granted".
I followed the example to get the fitness API on the google developer console and OAuth Client ID. But I don't know how to set it in my flutter app if it is needed. Thank you.
I've got it working by following this advice on the package Github repo. But I am open to more answers. Thanks
[Updated]
This solution can cause conflict and raise the "version solving failed" exception when using it together with the location package.
The best way, for now, is to use health: 3.0.4 as a workaround.
Related
I implemented google login in flutter without using firebase in flutter (google cloud console). It was working in apk then later I needed push notification service for which I used firebase (fcm token and all) then I released the app to playstore but google login does not work. I keep getting apiexception error. Has anybody faced this issue? if yes any help would be highly appreciated.
I do not have a specific answer to your problem but I have also faced this problem once, I accidentally resolved it though.
But Error 12500 is a general error code that may occur when attempting to use the Google Sign-In feature and is caused by a few potensial issues:
An issue with the SHA-1 fingerprint of your app's signing
certificate: To use Google Sign-In, you need to configure your app's
SHA-1 fingerprint and package name in the Firebase console. Make
sure that the fingerprint and package name you have configured in
the Firebase console match the ones you are using to sign your app.
An issue with the Google Services configuration file: Make sure you
have properly added the Google Services configuration file to your
app.
An issue with the Google Play Services library: Make sure you have
the latest version of the Google Play Services library installed in
your app.
An issue with the device or emulator you are using: Make sure you
are testing on a device or emulator that has Google Play Services
installed and is up to date.
Possible fixes to try/check:
Double-check the SHA-1 fingerprint and package name: Make sure that
the SHA-1 fingerprint and package name you have configured in the
Firebase console match the ones you are using to sign your app.
Make sure you have added the Google Services configuration file: The
Google Services configuration file is required for your app to
communicate with Google services, including Google Sign-In. Make
sure you have properly added this file to your app.
Update the Google Play Services library: Make sure you have the
latest version of the Google Play Services library installed in your
app. You can check for updates by going to the "SDK Manager" in
Android Studio.
Test on a device or emulator with Google Play Services installed:
Make sure you are testing on a device or emulator that has Google
Play Services installed and is up to date.
I hope this helps! I will quickly search if I can find any other solution.
I am using flutter 1.22.5 and Facebook plugin flutter_facebook_login: 3.0.0
to provide feature of Sign in with Facebook. Currently facing this error.
App not active: This app is not currently accessible and the app developer is aware of the issue. you will be able to log in when the app is reactivated
For other dependency I am not allowed to update flutter or Facebook plugin version.
Can someone guide me, Thanks in advance.
This answer is recent and may help. The error may not be linked to your code, but I recommend that you try to update your code to a SDK latest Flutter version.
I tried to use flutter for web with syncfusion library. I ran into compilation issues. Has anyone tried that integration ?
I used flutter channel beta (since my development was targeted for web and mobile both)
We have tried to replicate your scenario, unfortunately, we are not able to replicate any compilation issues while running on the web. So, kindly please make sure that you are using the current version of our chart widget 18.1.46. If you are not using the current version, please upgrade to the current version and try to replicate the issues and revert us with more information on the compilation issues and a sample attachment would be appreciable so that it will be helpful in providing the solution sooner.
And also, please follow the instruction in the link below to build the flutter application in the web.
https://flutter.dev/docs/get-started/web.
Note: I work for Syncfusion
I am trying to integrate ads in my android app through Heyzap. However, when i open the heyzap mediation suite, some of the third party sdks are marked with "missing permissions". these are AdColony, AppLovin, ChartBoost and Vungle. They all have "Sdk detected", "all activities found" and "credentials found" marked with green. the other sdks have "all permissions found". The thing is that when the app is trying to fetch an add it crashes.
What I would like to know if these crashes have anything to do with the sdks with missing permissions and if yes, how can i solve this problem?
I read "how to"s for each sdk and put all the mentioned permissions in my manifest but still nothing.
Can you, please, help me?
I was getting the same Missing Permissions error for Vungle, Applovin, Chartboost and AdColony.
For me removing android:maxSdkVersion="18" from the WRITE_EXTERNAL_STORAGE permission in the Vungle manifest made the issue disappear for all four networks. By Vungle manifest I mean the AndroidManifest file in Plugins/Android/Vungle_lib
As per Google specification the permission is not needed any more for API level 19 and above so I guess that's why Vungle adds the parameter. But somehow the Heyzap Mediation Suite keeps telling us that we are missing permissions. My guess is that there's something wrong with the Heyzap Mediation Suite since ad serving works even with the Missing Permissions warning.
I have followed the new Google Firebase guide for Facebook sign-in on Android but I am consistently getting the following error on a particular device.
FirebaseAuth:signInWithCredential failed
com.google.firebase.FirebaseApiNotAvailableException: API: InternalFirebaseAuth.FIREBASE_AUTH_API is not available on this device.
On other devices it seems to work fine. The device is Moto X Play running Android 6.0.1. It also has Google Play Services 9.0.83. I tried a complete uninstall and reinstall with no luck.
This was a bug affecting the 9.0.0 and 9.0.1 versions of the SDK. It has been fixed as of SDK version 9.0.2.
Update the Google repository via the Android SDK manager and then change your gradle dependency to:
compile 'com.google.firebase:firebase-auth:9.0.2'
See incident details here.
As Alfonso says in the comments, there is an issue we are seeing where some users don't have the Firebase Auth API available even though they have Google Play services 9.0.83.
That's a bug - sorry about that - and is being investigated at the moment. If you're seeing it, please raise an issue in the troubleshooting page with any further details of the device where you had the problem.