I have developed an app using Android Studio, which include login and register activities. when I copied my code to my new computer I have launched the app for the first time and it worked just fine. The day after, when I was trying again to launch the app once again. I wasn't able to sign-in to an existing user. I even could not create a new one. Does someone have any idea what caused it' and how could it be fixed?
Your question has no details at all..
Do you store the user credentials on a db?(it could be that you cannot login because you didn't connect correctly to the db) which type of db? is a Web service to an admin panel or some code posted on a hosting/vps?
Find out which is the error inside the logcat and post ONLY the error, maybe the stacktrace can help you.
So you can launch the app but the data inside is missing(credentials).. Do you see everything as usual or are there any images/details missing?
Stupid but easy to forget: do you have an active internet connection on the emulator?
have you tried to debug the code, have to tried to debug at least the authentication/register process?
Add more details, check your manifest is ok and you have all the permissions(internet, wifi or anything else), post the logcat error(if there is an error) or post the debug error, then someone can answer
Related
When I post a form with an image taken from my phone I reserve the error "413 request entity too large" I realize that an image included in the form taken by the phone camera is too large, and the server rejects the request... but how can I fix this issue, I'm using Java Spring framework, and MySQL database, all of this handled with Amazon aws services.
You have to modify your .platform as shown in the docs.
For example, you could have the following .platform/nginx/conf.d/myconfig.conf with content:
client_max_body_size 20M;
I struggled with this for so long until I came across this post:
https://medium.com/#robin.srimal/how-to-fix-a-413-request-entity-too-large-error-on-aws-elastic-beanstalk-ac2bb15f244d
Couple things to watch out for here, if your server is restarted or you deploy a new version etc, then your nginx server will also reset and you will need to perform these changes again. Also periodically, AWS seems to reset your EC2 instance address, not sure why, but you need to perform these changes again afterwards. There must be a way of making these changes permanent but I haven't figured that part out yet.
I find the solution thanks for helping...
1-I connect to my EC2 instance throw the "connect" button, a terminal appears.
2-I edit this file: etc/nginx/nginx.conf
3- Add this line:client_max_body_size 10M;
and it works fine.
thank you all ;
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've integrated Google inApp billing in my android App. It was working fine, But now I noticed that on one device its always returning BILLING_RESPONSE_RESULT_ERROR response. In Logcat it shows following error.
BillingClient: getSkuDetails() failed. Response code: 6
I couldn't find any help regarding this issue, Can someone help me what could be the possible problems and solution. Thanks.
This generally happens when you have signed out from Google account in your device. All you need to do is just sign in again, if needed do a full restart.
Well, my situation is the connection between my device and google's servers is unstable.Try to open the GooglePlay,and check if the connection is healthy.And it wroks.
In my case, this happened when a new app I submitted was in "Draft" status, not yet approved by Google. Just wait until it's approved and payments will start to work.
An alternative would be to submit it in the internal track and add the email for you play account as a test user.
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 have and android app in which i want to Post image and message to faceboook. I Have completed all Steps including facebook key from console hash key from program and save to facebook console. So when i run App it is posting image and message successfully only from my device in which same facebook account is used. But When i try from any other device it is not posting data to facebook and it gives me error "publish permission [publish action] not accepted by user". i got stuck at this point. please help me. what should i do. I read some articles and got idea that facebook change its policy and app should send to review. but i have not idea what and how necessary credentials required to facebook. please help me i have to complete my app as soon as possible. i am already getting late. i am searching from 2 weeks but at last decided to post question here. please help me. thanks in advance.