I have a single project which is synced on two different machines. I have Android Studio and the emulator successfully installed on both machines. I also have successfully implemented Firebase + Google authentication. When I open the emulator on the first machine and run the app, everything works fine but when I run the same project on the second machine using the same user, the authentication fails. If it try to print the error it says:
Google sign in failed! Error 10:
How can I make both authentications work on both machines? Thanks!
You have to add the SHA-1 key of the second machine in your firebase project.
The process is well explained already in this post. Please check it out in case you need clarification.
Related
I tried creating multiple new projects and made sure that all codes in several files are correct. I'm quite new to this and have never encountered this problem previously. After using the assistant to connect to firebase, it opens up the browser, asks me to login and ask for permission. After clicking the accept, a new window opens up with "localhost:55842/" and what happens to Android Studio, it will be giving a response "Firebase: Received a request from an invalid host firebase". Is there any way I can fix this? I have tried using previous version of IDEs but the only difference is that the connection succeeds but it can't receive or save data into the firebase.
Please make sure you turn off any antivirus and firewall temporary to enable firebase assistant connect flow running.
Android Studio choose random listening port each time we try to connecto to firebase web console, so we can't simply just allow one port in firewall/antivirus for android studio, completely disable is the only option
In my case, Avira antivirus is the cause, disable real time scan and then firebase connect flow running as expected (tried on Android Studio 3.6.1)
Hi I am not sure if you have solved this problem. I was facing the same issue. So it's the problem with the JSON file since android studio stores everything in the build it might have few older files conflicting with new file so I went ahead and deleted the old build file and restarted my android studio with the project and everything was working fine after.
I'm currently trying to solve an issue with a mobile application that is throwing a "Error communicating with application service' alert upon being launched.
The error occurs on both ios and android versions of the app across
multiple device's, wifi, 4G etc.
An emulation of the application using Android Studios DOES work. The
app successfully communicates with the sites API. I can see all of
this information on the logcat within Android Studio.
The mobile application has not been updated recently, the local version i'm
running the emulation with is identical to the live version. The app
hasn't been updated prior to the error occurring.
The domain/URL that the application is connecting to has recently had
a Certificate Signup Request generated for the SSL certificate that expires
in a few months. I'm not sure if this is relevant however I have read
that a emulated device handles https differently to an actual device.
To further diagnose the issue on an actual device I'm looking into "tcpdump" as it can potentially show everything that is happening on the device. I've tried using LogcatExtreme but it doesn't show a more verbose detailing of the error that is occurring.
Here is a link to the application that you can download right now. If anyone believes this is a security risk, please let me know and I will take it down. https://play.google.com/store/apps/details?id=au.com.silkhospitality.Silk
Even though I haven't exhausted all avenues of diagnosis I wanted to ask the community before I potentially end up in a culdesac.
Both the Android and iOS version of the application in question were redeployed to their respective app stores in order to solve this. The real reason for them failing to connect to the application was never discovered. These applications were both 5+ years old and needed some minor environmental changes to be made but none of the core programming was changed/altered in order to successfully redeploy.
I am using Jmeter 2.13 version and with that I used to record many scripts earlier successfully without any issue . Now, my OS has been reinstalled and I am holding Windows 8.1 , 64 bit version.After re installation, I am not able to record HTTPS web applications even though my proxy configuration is correct. After I setup everything in Jmeter, and click on start from work bench and I navigate to the browser try to access the application, it shows "Server not found" message.
However, the scripts which I saved earlier are working fine without any issues. only the new recording is not working.
Help me with the possible solutions.
"Server not found" indicates that browser is unable to access Internet (or intranet).
Most likely you're sitting behind the corporate proxy server and in previous JMeter installation you had these proxy server details specified in system.properties file like:
http.proxyHost=10.20.30.40
http.proxyPort=3128
https.proxyHost=10.20.30.40
https.proxyPort=3128
Double check with your network administrator if this is the case, if yes - take steps from Using JMeter behind a proxy User Manual chapter.
You can also try out JMeter Chrome Extension as an alternative solution - in that case you don't have to worry about proxies and SSL certificates substitution.
I'm trying to send push notification from my Java backend to my mobile app. For that, I'm using notnoop java-apns library.
I managed to set everything up and everything works perfectly on Development (Development certificate and provisioning profile).
I want to release the app soon but first I wanted to setup everything so that I'm ready once it's live. So I created an 'App Store and Ad Hoc' certificate, and also an 'Ad Hoc' provisioning profile.
Then I'm trying to use that P12 file which should be the same as the one I will be using once the app is live.
But unfortunately I'm getting the following exception:
java.net.SocketException: Connection closed by remote host
at sun.security.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1510)
at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:123)
at java.io.OutputStream.write(OutputStream.java:75)
at com.notnoop.apns.internal.ApnsConnectionImpl.sendMessage(ApnsConnectionImpl.java:328)
at com.notnoop.apns.internal.ApnsConnectionImpl.sendMessage(ApnsConnectionImpl.java:312)
at com.notnoop.apns.internal.ApnsServiceImpl.push(ApnsServiceImpl.java:46)
at com.notnoop.apns.internal.AbstractApnsService.push(AbstractApnsService.java:56)
at com.notnoop.apns.internal.ApnsServiceImpl.push(ApnsServiceImpl.java:36)
at com.notnoop.apns.internal.AbstractApnsService.push(AbstractApnsService.java:45)
.....
Anyone know what might be happening? How is it possible to work fine on Development but not AdHoc (and I'm guessing production as well, since they're using the same Push Notification certificate)?
I found the answer immediately after posting the question!
Basically, in development mode I had the following code to initialize the service:
this.service = APNS.newService().withCert(p12Stream, passphrase).withSandboxDestination().build();
But, when using a production certificate, you can no longer using the sandbox destination but instead you need to use the following:
this.service = APNS.newService().withCert(p12Stream, passphrase).withProductionDestination().build();
my app connects to another app service and transfer some data. i configure permissions in manifest file and everything works fine. but i i have a big problem. my app works and connect properly to that service if only installed after that service! if i first install my app and then install that service, i doesn't work and i get this error:
Not allowed to bind to service Intent
even i restart my phone it doesn't effect! what is the problem here?
This is a known (by design/won't fix) issue with custom permissions - you cannot use a custom permission if it is not known to the system at the time when your app is installed.
Since the custom permission is defined in the manifest of the service apk which hasn't yet been installed, the system doesn't know about it when setting up the actual permissions of your client app, so it is effectively filtered out.
You will need to either get your users to install the service apk before the client, or else use some other scheme than a custom permission. For example, you might be able to do something by allowing any app to talk to you, but only responding to those with a key of some sort (though keys can be extracted by reverse engineering...)