Develop Reference

Getting file not found exception while trying to connect with url in android studio.How to solve this?

I am trying to connect to mysql using wampp and the following error is thrown how to solve this?
W/System.err: java.io.FileNotFoundException: http://192.168.2.198/login.php
at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:250)
at com.example.mysqltest.BackgroundWorker.doInBackground(BackgroundWorker.java:46)
at com.example.mysqltest.BackgroundWorker.doInBackground(BackgroundWorker.java:19)
at android.os.AsyncTask$2.call(AsyncTask.java:304)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:243)
W/System.err: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)

There are following possibility to occur this issue
maybe your project or file location is not perfect
maybe because of the port number or IP not match time of calling
First, try to run this page in your mobile browser web browser and it will work in mobile browser then it will work in API definitely if not work then you need to change in your config

Buffer Overflow - No available Space crash in Android

So, I'm constantly getting this buffer overflow crash (393238).
One example, I've just fixed is, when I run Log.d("test", null) I get the crash.
If I remove this line of code, there's no crash.
As far as I know, every single bug in my code, whether it's an ArrayOutOfBounds, Incorrect Type, Null Exceptions, etc. are all causing Buffer Overflow crashes.
I don't know why this is happening. Why is Android not gracefully handling and returning Exception messages, rather than crashing the program with a Buffer Overflow message all the time?
Also, I've tried running on my own phone through usb debugging, Nexus emulator, etc. Still happens.
Here is the exact message:
W/ErrorProcessor: onFatalError, processing error from engine(4)
com.google.android.apps.gsa.shared.speech.a.g: Error reading from input stream
at com.google.android.apps.gsa.staticplugins.recognizer.i.a.a(SourceFile:342)
at com.google.android.apps.gsa.staticplugins.recognizer.i.a$1.run(SourceFile:1367)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at com.google.android.apps.gsa.shared.util.concurrent.a.ak.run(SourceFile:66)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
at com.google.android.apps.gsa.shared.util.concurrent.a.ad$1.run(SourceFile:85)
Caused by: com.google.android.apps.gsa.shared.exception.GsaIOException: Error code: 393238 | Buffer overflow, no available space.
at com.google.android.apps.gsa.speech.audio.Tee.g(SourceFile:2531)
at com.google.android.apps.gsa.speech.audio.ap.read(SourceFile:555)
at java.io.InputStream.read(InputStream.java:101)
at com.google.android.apps.gsa.speech.audio.al.run(SourceFile:362)
at com.google.android.apps.gsa.speech.audio.ak$1.run(SourceFile:471)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at com.google.android.apps.gsa.shared.util.concurrent.a.ak.run(SourceFile:66)
at com.google.android.apps.gsa.shared.util.concurrent.a.ax.run(SourceFile:139)
at com.google.android.apps.gsa.shared.util.concurrent.a.ax.run(SourceFile:139)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607) 
at java.lang.Thread.run(Thread.java:761) 
at com.google.android.apps.gsa.shared.util.concurrent.a.ad$1.run(SourceFile:85) 

I had the same thing. My app ran fine on my main computer from android studio on both a real android tablet and the tablet emulator. When I did the exact same thing on my laptop I got this crash, for both real device and emulator.
I ended up 'fixing it' by deleting the project build directory, and doing a Tools->AVD Manager->Actions Wipe Data. I then rebuilt/ran the project and it worked. Go figure...

GsaIOException Buffer overflow, no available space

I have a MediaPlayer app with a live streaming function. When I test the app with a physically device(API 22 Lollipop and API 23 Marshmallow) there are no problems with starting of the stream.
Today I want to test the application with a Emulator (API 25 Nougat). Stream is not working and I get the following error:
(SourceFile:139)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607) 
at java.lang.Thread.run(Thread.java:761) 
at com.google.android.apps.gsa.shared.util.concurrent.a.ad$1.run(SourceFile:85) 
02-23 23:58:09.834 2166-3554/com.google.android.googlequicksearchbox:search W/ErrorProcessor: onFatalError, processing error from engine(4)
com.google.android.apps.gsa.shared.speech.a.g: Error reading from input stream
at com.google.android.apps.gsa.staticplugins.recognizer.i.a.a(SourceFile:342)
at com.google.android.apps.gsa.staticplugins.recognizer.i.a$1.run(SourceFile:1367)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at com.google.android.apps.gsa.shared.util.concurrent.a.ak.run(SourceFile:66)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
at com.google.android.apps.gsa.shared.util.concurrent.a.ad$1.run(SourceFile:85)
Caused by: com.google.android.apps.gsa.shared.exception.GsaIOException: Error code: 393238 | Buffer overflow, no available space.
at com.google.android.apps.gsa.speech.audio.Tee.g(SourceFile:2531)
at com.google.android.apps.gsa.speech.audio.ap.read(SourceFile:555)
at java.io.InputStream.read(InputStream.java:101)
at com.google.android.apps.gsa.speech.audio.al.run(SourceFile:362)
at com.google.android.apps.gsa.speech.audio.ak$1.run(SourceFile:471)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:428)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at com.google.android.apps.gsa.shared.util.concurrent.a.ak.run(SourceFile:66)
at com.google.android.apps.gsa.shared.util.concurrent.a.ax.run(SourceFile:139)
at com.google.android.apps.gsa.shared.util.concurrent.a.ax.run(SourceFile:139)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607) 
at java.lang.Thread.run(Thread.java:761) 
at com.google.android.apps.gsa.shared.util.concurrent.a.ad$1.run(SourceFile:85) 
I can recognize only one thing where I think it is important.
GsaIOException: Error code: 393238 | Buffer overflow, no available space
But I don't know what it could mean. Can anyone explain what kind of Exception it is. And where I can search at the code to find the problem?

I had a similar issue, for me it was crashing on devices too, with the same error. This is how I fixed it for devices:
<uses-permission android:name="android.permission.RECORD_AUDIO" />
More details here: Looping Error on Android Emulator
To make the app work on simulator, after applying the fix from the above link, I had to create a new simulator based on x86 architecture (not x86_64 as before) and it worked.

I was getting these exact messages while trying to debug my device with logcat. Could not figure out where they were coming from. Finally realized that a preceding debug session with the emulator was generating these. I simply quit the emulator to stop them.

I did receive the same issue, and i did the following things to make this crash occurs.
Few api's that i wrote needed to allocate some memory since a file needed to be parsed and kept in that buffer. I started parsing the file without allocating the buffer hence received that message.
So you could look into similar code where you might be doing the same.

I've resolved this by deleting the apk files that i have created before and they still remain in Project Files list.

Unable to get the exact reason of crash while using Realm + Okhttp

I am using Realm and my app crashes with the following traces and I don't get any idea to resolve this. This is the only stack strace that I see on the console. Nothing else :
FATAL EXCEPTION: OkHttp Dispatcher
java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.Object.equals(java.lang.Object)' on a null object reference
at io.realm.RealmConfiguration.equals(RealmConfiguration.java:186)
at io.realm.RealmCache.validateConfiguration(RealmCache.java:217)
at io.realm.RealmCache.createRealmOrGetFromCache(RealmCache.java:103)
at io.realm.Realm.getInstance(Realm.java:213)
at io.realm.Realm.getInstance(Realm.java:176)
at testapp.WebClient.WebClientAPICalls$2.onResponse(WebClientAPICalls.java:74)
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:133)
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
This is the line 74: Realm realm = Realm.getInstance(context);
I am not sure what the exact reason is for this crashing. Any help in this regard is highly appreciated.

So just for the information to the people out here, as confirmed by # Christian Melchior, it was a bug with the latest version of realm 0.88.0.
Hence I had to rollback to the version 0.87.5 for now in order to resolve the issue.
Christian Melchior, who works at #Realm.io has also confirmed that they are releasing a fix for this bug as soon as possible and hence the latest version should be good to go.

Identity Toolkit API for android

Im trying to execute the Android Identity Toolkit example from Google: https://github.com/googlesamples/identity-toolkit-android .
But, when I tried to execute the tutorial it gives me the next stack trace:
06-17 12:04:00.450 12306-12339/com.google.identitytoolkit.demo E/GoogleIdpClient﹕ Unrecoverable auth exception: Unknown
com.google.android.gms.auth.GoogleAuthException: Unknown
at com.google.android.gms.auth.GoogleAuthUtil.getToken(Unknown Source)
at com.google.android.gms.auth.GoogleAuthUtil.getToken(Unknown Source)
at com.google.identitytoolkit.idp.google.GoogleIdpClient$1.call(GoogleIdpClient.java:126)
at com.google.identitytoolkit.idp.google.GoogleIdpClient$1.call(GoogleIdpClient.java:120)
at com.google.identitytoolkit.executor.ProgressRequestExecutor$2.doInBackground(ProgressRequestExecutor.java:84)
at com.google.identitytoolkit.executor.ProgressRequestExecutor$2.doInBackground(ProgressRequestExecutor.java:71)
at android.os.AsyncTask$2.call(AsyncTask.java:288)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:841)
06-17 12:04:00.475 12306-12306/com.google.identitytoolkit.demo E/ViewRootImpl﹕ sendUserActionEvent() mView == null
I tried to find some iformation about that exception, but I cant find anything clear, or anything I can use as a solution.
I did all the steps which Google say to do: https://developers.google.com/identity/toolkit/android/quickstart but still not working, probally I did something wrong. Can you help me?

I think, a lot can trigger the exception with so much configuring going on. I got the same exception. For me, the issue is in the AndroidManifest(I got everything right in the developer console configuration).
My first mistake:
android:scheme is given "Client ID for Android" instead of "Client ID for web application"
My next mistake: (I think this one is really causing the unknown exception)
identitytoolkit.server_client_id is given "Key for web applications" instead of, again, "Client ID for web application"(this time without modifying reverse like above)