I am trying to connect to Googlefit but i am getting a strange error code as below
E/GooglePlayServicesUtilďą• Unexpected error code 5005
Does anybody have any idea about this.Thanks In advance
I solved the error with the help of the answer in this post:
https://stackoverflow.com/a/28391583/2977169
#Sumoanand:
I also faced similar problem.
This issue occurs if app is not registered properly in google developer console.
I think you have registered app on Google developer Console using production keystore certificate fingerprint(SHA1) where as you are testing it on app which has debug keystore.
Perform following steps:
Create one more client Id using debug keystore certificate fingerprint(SHA1).
Uninstall existing app.
Install app & connect to Google fit.
Check under google fit app & make sure that your app is listed as a connected app (... > Settings > Connected apps > Connected apps & devices).
Now run the above code & it will work !!!
I had this error and the consent screen had been filled in correctly. The only way I could get around this was to delete the project and re-create it.
I changed my device date time to past time before connect to Google Fit and I got error 5005.
After changed to current time, it works :)
Related
I'm very new to React Native and I'm understanding now Ports and similar things. In the last days I was able to access through Expo Go my app, but starting from today I ran into issues.
I think the problem was, that I was accessing the app using an university wi-fi connection, while the other days I used a mobile data connection. With Wi-Fi I was not able to access the app. The error log said: java.net.connectException: failed to connect to (...)
So I started a big journey thorugh ports, ip addresses and firewall, arriving to the ubuntu's ufw. Actually I don't know exactly what I've done, but the last try was to disable everything (like it was at the beginning) and retrying to access the app, nothing changed. The error log was: java.net.SocketTimoutException: failed to connect to (...) from (...)
I tried also use tunnel (like this question says Unable to connect to Expo React Native Project on WSL2 with Expo Go on phone) but it didn't help. In this case, the app says New update avalable: downloading... but never ends.
So, any suggestion to understand a) which is the real problem (a part that I've done something that I didn't understand) and b) how to solve it ?
I have installed maximo-anywhere version 7.6.3. This is just a development environment using the simulator with mobilefirst on eclipse.
I am currently unable to login with the following message. Not authorized when logging into Maximo Anywhere - on other environments I have created I have just given the user the correct security group... however in this scenario even though I have deployed the WorkExecution application and provided the user with the ANYWHERE_TECHNICIAN security group the user is still unable to login.
Any thoughts? Has anyone come across this issue?
Login failure
This issue is related to HTTP/HTTPS. It looks like anywhere is currently unable to go over HTTPS.
The error message was just a rogue message throwing it off.
Thanks
I was debugging my app in my personal Google play services account but the company I am working on has already got their Google play services account so I changed and DELETED (deleting api credentials and unpublished it) the game. I have managed to register a new android app but when I try to register a web app I get the error #4800004 (An unexpected error has occurred. Try again later).
What should I do?
It can take approx 7 days for your old package to be removed. You will not be able to add a new one until that happens.
Your options:
Wait 7 days and try again.
Rename your package.
Alternately: You cannot have two apps with the same package details. Are your two apps conflicting with each other?
From the github post, it was mentioned that you maybe re-registering an app with the same package name. You can check if your project was already registered in the console. Projects that you have deleted will take effect after the 7th day.
For further information, you can also try to check this page. It may also have something to do with SHA1 Signing Certificate Fingerprint from android studio.
You need to make sure that the LaunchURL that you provide includes the protocol (for example: http://) in addition to the domain. If you do not provide the protocol, google appears to automatically add https://, but this led to the error posted in the question for me.
I try to run a simple test.
Everything is fine in the simulator, when i run on the device, emerge following error:
The Log is "dyld: could not load inserted library '/private/var/mobile/Containers/Data/Application/7EE29748-5E86-4E9B-B8E5-882753654F87/tmp/IDEBundleInjection.framework/IDEBundleInjection' because no suitable image found. Did find:
/private/var/mobile/Containers/Data/Application/7EE29748-5E86-4E9B-B8E5-882753654F87/tmp/IDEBundleInjection.framework/IDEBundleInjection: code signature invalid for '/private/var/mobile/Containers/Data/Application/7EE29748-5E86-4E9B-B8E5-882753654F87/tmp/IDEBundleInjection.framework/IDEBundleInjection'
"
I tried to make Clean & Build and remove derived data, it didn't help me.
I appreciate any tips or helps
This was due to me changing my appleID password. If you sign back in Xcode -> Preferences -> Accounts, this fixes the problem.
I struggled with this problem for the whole afternoon and finally found my solution. Yes it is about the certificates again.
I heard the news that Apple's world developer relations certificate expired but never realized it'll become a problem until now.
In my keychain all the developer identifies appeared with the red status as "This certificate was signed by an unknown authority".
So the solutions is, go to http://www.apple.com/certificateauthority/ and download "Worldwide Developer Relations - G2 Certificate", import it into your keychain, check the status of your developer identity certificate and if it turns green (valid), the unit testing problem should be fixed.
In our ipad application user has to enter his details for registration. After user enter his details we save those details in the Device's keychain. So next time user launched the app user can use the app without registering again. Since we save it in the keychain even the app reinstall by deleting is also works fine.
To write to key chain we use sskeychain class as most developer do. This feature is working properly in devices without any issue.
One of our client use their symantec (unitymobile) mdm to distribute this app to their users. But when user install it through the mdm app gives following error when saving data to the key chain.
"The operation couldn’t be completed. (com.samsoffes.sskeychain error
-34018.)"
Initially we thought this is due to one of the policies they have included. But no luck. Can some one please tell me what has happened here and how to solve this issue.
P.S.
Actually underlying error was this.
(OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)