Can't Repro
Status Update
Comments
uc...@google.com <uc...@google.com>
d4...@gmail.com <d4...@gmail.com> #2
Err, I have no idea how gerrit changesets are reflected in the bug report, but there is a preliminary patch https://android-review.googlesource.com/#/c/159020/
ke...@google.com <ke...@google.com> #3
Scope of changes to bionic are somewhat more complex than initially thought.
The troublesome spots are mmap() and friends, malloc() and friends (due to symbol clash between struct, fieldname, and function names) as well as most of the routines in string.h
string.h exposes some issues, because the routines in it are both defined as inline functions that call out to assembly counterpart of the same name using an inconsistent __builtin_XXXX() convention. Sometimes the routines are available as _builtin___XXXX_chk and sometimes as __builtin_xxx.
I initially thought about limiting the macro magic purely for bionic/arm64, but there does not seem to be a nice way to do this.
Does this mean I need to touch all the .S files that are associated with string.h?
Even for the ones that are NOT for arm64?
Please take a look at:
https://code.google.com/p/android/issues/detail?id=180578
The troublesome spots are mmap() and friends, malloc() and friends (due to symbol clash between struct, fieldname, and function names) as well as most of the routines in string.h
string.h exposes some issues, because the routines in it are both defined as inline functions that call out to assembly counterpart of the same name using an inconsistent __builtin_XXXX() convention. Sometimes the routines are available as _builtin___XXXX_chk and sometimes as __builtin_xxx.
I initially thought about limiting the macro magic purely for bionic/arm64, but there does not seem to be a nice way to do this.
Does this mean I need to touch all the .S files that are associated with string.h?
Even for the ones that are NOT for arm64?
Please take a look at:
d4...@gmail.com <d4...@gmail.com> #4
Could you please reiterate why is it not possible to fix this in TSan? If the problem is some call happening before __tsan_init, we just need to call __tsan_init right there. Most (if not all) interceptors have this logic.
Does it still happen if __tsan_init is called from .preinit_array?
Does it still happen if __tsan_init is called from .preinit_array?
d4...@gmail.com <d4...@gmail.com> #5
Its troublesome before __tsan_init because we lack __thread keyword support in bionic. I had to hack in a workaround in TSAN that does not use intercepted calls. (more on this below)
The majority of the problem actually occurs after __tsan_init has been called.
For example, pthread_create() calls a bunch of routines for the *new thread*, before it has had a chance to initialize its ThreadState. All of these routines running on the new thread are intercepted by tsan, and crashes because ThreadState has not been initialized yet.
A purely tsan-only fix is to "globally ignore" interceptors during troublesome times. This works fine for two threads, but doesn't scale to multiple threads - now you can miss events because they are being ignored.
I also tried putting in "global partial ignores" (i.e. ignore interceptors only on the new thread), but that got really hairy as well.
The fundamental problem is that TSAN is intercepting calls that it has no business intercepting.
For example, the same thing happens during thread join time, when one thread is being deconstructed.
Similar things happen during process exit time where ALL threads are being deconstructed.
Playing around with purely TSAN solution, all I managed to do was move around the actual place of the crash/hang/missed events.
The majority of the problem actually occurs after __tsan_init has been called.
For example, pthread_create() calls a bunch of routines for the *new thread*, before it has had a chance to initialize its ThreadState. All of these routines running on the new thread are intercepted by tsan, and crashes because ThreadState has not been initialized yet.
A purely tsan-only fix is to "globally ignore" interceptors during troublesome times. This works fine for two threads, but doesn't scale to multiple threads - now you can miss events because they are being ignored.
I also tried putting in "global partial ignores" (i.e. ignore interceptors only on the new thread), but that got really hairy as well.
The fundamental problem is that TSAN is intercepting calls that it has no business intercepting.
For example, the same thing happens during thread join time, when one thread is being deconstructed.
Similar things happen during process exit time where ALL threads are being deconstructed.
Playing around with purely TSAN solution, all I managed to do was move around the actual place of the crash/hang/missed events.
d4...@gmail.com <d4...@gmail.com> #6
On x86_64/linux, precisely zero calls are intercepted during pthread_create() on the new thread until it has finished initializing its ThreadState.
That does not happen on aarch64/bionic
That does not happen on aarch64/bionic
ke...@google.com <ke...@google.com> #7
Oh, the reason why I had to hack in a non-interceptible TLS workaround was that intercepted calls happen during pthread_key maintenance that occurs both during pthread_join time as well as at exit time.
What was happening when I was using pthread_get/setspecific() was that after a thread was destroyed, an intercepted call was GENERATING a NEW key for the dead thread. Hilarity ensued afterwards.
What was happening when I was using pthread_get/setspecific() was that after a thread was destroyed, an intercepted call was GENERATING a NEW key for the dead thread. Hilarity ensued afterwards.
d4...@gmail.com <d4...@gmail.com> #8
Back to the topic at hand,
does anyone have any ideas on how to limit the bionic headerfile changes purely for aarch64?
https://code.google.com/p/android/issues/detail?id=180578
I *think* it might be better to limit the new internal symbols to 64bit arm parts, but there does not seem to be a nice way to do this (yet).
While my build currently "works", I don't think it will build for other platforms (i.e. 32bit arm, mips etc...)
Thanks
does anyone have any ideas on how to limit the bionic headerfile changes purely for aarch64?
I *think* it might be better to limit the new internal symbols to 64bit arm parts, but there does not seem to be a nice way to do this (yet).
While my build currently "works", I don't think it will build for other platforms (i.e. 32bit arm, mips etc...)
Thanks
ke...@google.com <ke...@google.com> #9
It looks like __aarch64__ is defined for Clang builds. I am not sure about gcc, nor can I say that the bionic folks are going to be pleased with architecture-specific stuff polluting high-level headers.
d4...@gmail.com <d4...@gmail.com> #10
@11: i think he's confused and expecting __aarch64__ to be defined in code that's built 32-bit.
d4...@gmail.com <d4...@gmail.com> #11
No, not confused (at least I think)
So the crux of the matter is this.
I need to touch some .S files, which are necessarily architecture specific, to add in the private symbols we need to support TSAN.
I can either touch ALL .S files (arm, arch64, x86 ...), or just the ones that gets used while building a 64 bit device (even if they are 32bit libraries)
Now, is it OKAY for me to touch all the .S files?
If that is the case, thenhttps://code.google.com/p/android/issues/detail?id=180578 is moot.
OTOH, If you guys want me to scope my changes purely for 64bit arm devices, then
https://code.google.com/p/android/issues/detail?id=180578 DOES matter IF there are ever any cases where 64bit library/executable calls out to 32bit library
I hope this is clear
So the crux of the matter is this.
I need to touch some .S files, which are necessarily architecture specific, to add in the private symbols we need to support TSAN.
I can either touch ALL .S files (arm, arch64, x86 ...), or just the ones that gets used while building a 64 bit device (even if they are 32bit libraries)
Now, is it OKAY for me to touch all the .S files?
If that is the case, then
OTOH, If you guys want me to scope my changes purely for 64bit arm devices, then
I hope this is clear
d4...@gmail.com <d4...@gmail.com> #12
In other words,
if it is okay for me to touch all the variant memset.S and strlen.S files, then I do NOT need to have arch specific exceptions in the new .h files.
The downside is that its gonna be a bigger patch :-/
What do you guys think?
if it is okay for me to touch all the variant memset.S and strlen.S files, then I do NOT need to have arch specific exceptions in the new .h files.
The downside is that its gonna be a bigger patch :-/
What do you guys think?
d4...@gmail.com <d4...@gmail.com> #13
Hi everyone.
I upload a set of patches, all tagged with this bug.
I have no idea if your gerrit handles stacked patches well. (It didn't before)
If it does not, I can always upload a merged patch.
The rough order of patches are
1. new files + pthreads + mman.h
2. system calls (all the .S files and the gensyscalls.py)
3. string.h and friends
4. malloc.h and friends
5. ioctl/tcgetattr
Its not readily apparent what the order of the patches should be.
Here are the change-ids:
Support for Thread Sanitizer for Bionic
Change-Id: I724fb8d77059d3e01e1c4336d1aa2c0c550bbb80
Add new system call weak aliases, modified so that it is not arm64 specific
Change-Id: I0011bd344ba9ce977e429081a0cb84d8e59463fc
Touching all of string.h
Change-Id: I826f328a1849331dc39d5ff6847be02aff2ff1ba
Now touching malloc/free and friends
Change-Id: I5a2d07bfcf332556aeb0c3734b5ba122c80ee567
Now touching ioctl/tcgetattr
Change-Id: Ia709a5e7acf22239ad57aa22c06a867da6f6ef14
I upload a set of patches, all tagged with this bug.
I have no idea if your gerrit handles stacked patches well. (It didn't before)
If it does not, I can always upload a merged patch.
The rough order of patches are
1. new files + pthreads + mman.h
2. system calls (all the .S files and the gensyscalls.py)
3. string.h and friends
4. malloc.h and friends
5. ioctl/tcgetattr
Its not readily apparent what the order of the patches should be.
Here are the change-ids:
Support for Thread Sanitizer for Bionic
Change-Id: I724fb8d77059d3e01e1c4336d1aa2c0c550bbb80
Add new system call weak aliases, modified so that it is not arm64 specific
Change-Id: I0011bd344ba9ce977e429081a0cb84d8e59463fc
Touching all of string.h
Change-Id: I826f328a1849331dc39d5ff6847be02aff2ff1ba
Now touching malloc/free and friends
Change-Id: I5a2d07bfcf332556aeb0c3734b5ba122c80ee567
Now touching ioctl/tcgetattr
Change-Id: Ia709a5e7acf22239ad57aa22c06a867da6f6ef14
ke...@google.com <ke...@google.com>
ke...@google.com <ke...@google.com> #14
Hi.
I just pushed up a new changeset that combines the 5 mentioned above.
https://android-review.googlesource.com/#/c/162104/
(Apparently gerrit still can't handle stacked changesets without manual intervention.
It marked the 5 prior patches as "unmergeable")
I just pushed up a new changeset that combines the 5 mentioned above.
(Apparently gerrit still can't handle stacked changesets without manual intervention.
It marked the 5 prior patches as "unmergeable")
ke...@google.com <ke...@google.com> #16
d4...@gmail.com <d4...@gmail.com> #17
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO .
ke...@google.com <ke...@google.com> #18
Ah sorry about that David. I was able to unzip your project and test it out myself.
Unfortunately I didn't encounter any problem with stepping through your application. Can you try removing all sources for different API versions and redownloading them through the SDK manager?
Unfortunately I didn't encounter any problem with stepping through your application. Can you try removing all sources for different API versions and redownloading them through the SDK manager?
d4...@gmail.com <d4...@gmail.com> #19
Sorry it takes whole day to reinstall API.
But it doesn't work, i still have error when i try to move from main activity to fragment and when i try to run code above.
~First when i try to move to fragment, it also showed "source code does not match the byte code" on Log.java
~When i press F8 key it stuck on FastPrintWriter.java the lines loop exactly in order like this 623,625,291,292,301,302,306,307,308,629,629,654,657,658
~Since it loop there i try to resume program instead, but resulting SampleProject stopped
~Oddly when i try to run my original project i can move to fragments, yet i still can't run the code above. It just result "Unfortunately, Project has stopped" when i run it. I haven't debug my original project but i presume it has the same error.
~i install whole sdk platform for android 5.0, 5.1, and 8.0 except marked with android tv
Attach are the errors and sdk that i reinstall.
Hope the explanation helps. It just drive me crazy, please help where i do wrong here.
But it doesn't work, i still have error when i try to move from main activity to fragment and when i try to run code above.
~First when i try to move to fragment, it also showed "source code does not match the byte code" on Log.java
~When i press F8 key it stuck on FastPrintWriter.java the lines loop exactly in order like this 623,625,291,292,301,302,306,307,308,629,629,654,657,658
~Since it loop there i try to resume program instead, but resulting SampleProject stopped
~Oddly when i try to run my original project i can move to fragments, yet i still can't run the code above. It just result "Unfortunately, Project has stopped" when i run it. I haven't debug my original project but i presume it has the same error.
~i install whole sdk platform for android 5.0, 5.1, and 8.0 except marked with android tv
Attach are the errors and sdk that i reinstall.
Hope the explanation helps. It just drive me crazy, please help where i do wrong here.
d4...@gmail.com <d4...@gmail.com> #20
is the explanation and screen shot clear for you to locate the problem? please tell me if you need other data.
d4...@gmail.com <d4...@gmail.com> #21
Hello, it's been a while? Is there any data you need or info you can add for this issue?
d4...@gmail.com <d4...@gmail.com> #22
i'm desperate here? any info?
d4...@gmail.com <d4...@gmail.com> #23
Hello Kelvin, Is there any further explanation needed?
Or maybe you need another data?
I have tried reinstall it many times but it just wont worked.
Or maybe you need another data?
I have tried reinstall it many times but it just wont worked.
ke...@google.com <ke...@google.com> #24
Hi David,
Thank you for continuing to follow up on this issue and your patience. I tried again with your zipped project and instructions. But now I cannot build your project since it cannot resolve AppCompatActivity for me.
What version of Android studio are you using? Can you try again with the latest 3.2 canary?https://developer.android.com/studio/preview/index.html
Thank you for continuing to follow up on this issue and your patience. I tried again with your zipped project and instructions. But now I cannot build your project since it cannot resolve AppCompatActivity for me.
What version of Android studio are you using? Can you try again with the latest 3.2 canary?
d4...@gmail.com <d4...@gmail.com> #25
Hi Kelvin,
Previously i use android studio version 2.3.3, i try to update the platform yet it stuck on 3.0.1. I try to check for update again but it says i already used the latest update.
Funny thing is when i try to run the program,android virtual device said my system unable to handle 1,5GB ram, and it adjust itself to 512MB(this never happen on android 2.3.3).
Yet it just stuck on black screen, the device not starting at all
I try to make new android virtual device with 512MB, it run smoothly, but when i try to run the program it always restart.
And when i used my own device(not virtual one) the error is the same
If i download from the link you gave me, do i need to rebuild the program from scratch or i can import my previous code?
Previously i use android studio version 2.3.3, i try to update the platform yet it stuck on 3.0.1. I try to check for update again but it says i already used the latest update.
Funny thing is when i try to run the program,android virtual device said my system unable to handle 1,5GB ram, and it adjust itself to 512MB(this never happen on android 2.3.3).
Yet it just stuck on black screen, the device not starting at all
I try to make new android virtual device with 512MB, it run smoothly, but when i try to run the program it always restart.
And when i used my own device(not virtual one) the error is the same
If i download from the link you gave me, do i need to rebuild the program from scratch or i can import my previous code?
d4...@gmail.com <d4...@gmail.com> #26
Hi Kelvin,
Previously i use android studio version 2.3.3, i try to update the platform yet it stuck on 3.0.1. I try to check for update again but it says i already used the latest update.
Funny thing is when i try to run the program,android virtual device said my system unable to handle 1,5GB ram, and it adjust itself to 512MB(this never happen on android 2.3.3).
Yet it just stuck on black screen, the device not starting at all
I try to make new android virtual device with 512MB, it run smoothly, but when i try to run the program it always restart.
And when i used my own device(not virtual one) the error is the same
If i download from the link you gave me, do i need to rebuild the program from scratch or i can import my previous code?
Previously i use android studio version 2.3.3, i try to update the platform yet it stuck on 3.0.1. I try to check for update again but it says i already used the latest update.
Funny thing is when i try to run the program,android virtual device said my system unable to handle 1,5GB ram, and it adjust itself to 512MB(this never happen on android 2.3.3).
Yet it just stuck on black screen, the device not starting at all
I try to make new android virtual device with 512MB, it run smoothly, but when i try to run the program it always restart.
And when i used my own device(not virtual one) the error is the same
If i download from the link you gave me, do i need to rebuild the program from scratch or i can import my previous code?
d4...@gmail.com <d4...@gmail.com> #27
happy Chinese New year
d4...@gmail.com <d4...@gmail.com> #28
Update, Sorry for taking long time i have to reinstall windows since it was malfuctioned for couple weeks.
Anyway i installed android 3.2 cannary as you instructed but i cannot even run the project.
It says "Gradle sync failed: CreateProcess error=216, This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher
Consult IDE log for more details (Help | Show Log) (91ms)"
for your info my windows is 32 bit as well as my hardware component.
Any ideas Kelvin?
Anyway i installed android 3.2 cannary as you instructed but i cannot even run the project.
It says "Gradle sync failed: CreateProcess error=216, This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher
Consult IDE log for more details (Help | Show Log) (91ms)"
for your info my windows is 32 bit as well as my hardware component.
Any ideas Kelvin?
rp...@google.com <rp...@google.com> #29
#28: You probably downloaded the 64-bit version of Android Studio. Try to download the zip file that has the "32" suffix (for example: android-studio-ide-173.4615518-windows32.zip)
d4...@gmail.com <d4...@gmail.com> #30
was'nt android studio supposed to be global one? any way here is screeshot of folder and download page of android studio.
As you can see on the download page there is no 32 or 64 marking
And on the folder i do run the studio.exe not the studio64.exe
As you can see on the download page there is no 32 or 64 marking
And on the folder i do run the studio.exe not the studio64.exe
d4...@gmail.com <d4...@gmail.com> #31
Update: Sorry i install via exe files earlier and now i can run gradle with download of cannary version 5
But i found another bug, i try to use newly created Android Virtual Device, it have android lolipop 5.0 and memory card storage (see attachment avd config.jpg).
but when i started camera aplication, it says that i need to insert sd card (see attachment sd card problem avd.jpg)
Since android monitor is replaced by android profiler, i don't know how to add image manually. Which means i can't test the code on android 3.2.
Please kindly advise what wrong since i try to delete and create new AVD several times, and it always the same.
Or please kindly advice how to add files manually to AVD since all i can found on google is only via android monitor->file manager
But i found another bug, i try to use newly created Android Virtual Device, it have android lolipop 5.0 and memory card storage (see attachment avd config.jpg).
but when i started camera aplication, it says that i need to insert sd card (see attachment sd card problem avd.jpg)
Since android monitor is replaced by android profiler, i don't know how to add image manually. Which means i can't test the code on android 3.2.
Please kindly advise what wrong since i try to delete and create new AVD several times, and it always the same.
Or please kindly advice how to add files manually to AVD since all i can found on google is only via android monitor->file manager
d4...@gmail.com <d4...@gmail.com> #32
update: i change sd card setting on AVD to external by using path for android sdk folder -> emulator, ->mksdcard.exe, somehow the photo aplication works
But when i try to run the program i encounter the same error the only difference is no "source code does not match byte code" pop up but still on the same "}" where it crashed
I notice some strange event though:
1. toast don't come out on emulator eventhough when i press f8 the code run it.
2. on debug mode the picture is NOT saved on server, while when i'm NOT in debug mode the picture saved on server but still crashed and no toast pop up on AVD.
i also attached log where it record starting from the error to when AVD crashed, you can see that the upload success.
Please advise it's almost 1 year with no progress.
But when i try to run the program i encounter the same error the only difference is no "source code does not match byte code" pop up but still on the same "}" where it crashed
I notice some strange event though:
1. toast don't come out on emulator eventhough when i press f8 the code run it.
2. on debug mode the picture is NOT saved on server, while when i'm NOT in debug mode the picture saved on server but still crashed and no toast pop up on AVD.
i also attached log where it record starting from the error to when AVD crashed, you can see that the upload success.
Please advise it's almost 1 year with no progress.
d4...@gmail.com <d4...@gmail.com> #33
hello? is there any ideas? i'm stuck at this for half year already
ke...@google.com <ke...@google.com> #34
Regarding the AVD issue in https://buganizer.corp.google.com/issues/64589225#comment31 , please file a new bug to track that separately.
On the original issue of "source code does not match byte code", I'm still unable to reproduce the issue and have not seen other reports of this problem to help me debug it.
Unfortunately given the situation there are more urgent issues for the debugger team to fix. Thank you for your patience and for following up on this issue. If you want to try and provide a simple, standalone project with instructions to reproduce it on the latest studio version, I'll take another look at it.
On the original issue of "source code does not match byte code", I'm still unable to reproduce the issue and have not seen other reports of this problem to help me debug it.
Unfortunately given the situation there are more urgent issues for the debugger team to fix. Thank you for your patience and for following up on this issue. If you want to try and provide a simple, standalone project with instructions to reproduce it on the latest studio version, I'll take another look at it.
d4...@gmail.com <d4...@gmail.com> #35
Regarding https://issuetracker.google.com/issues/64589225#comment31 , the issue should be overcome by https://issuetracker.google.com/issues/64589225#comment32
Or That should not be the case?
If it not then i will make another thread for it, as for standalone project here is the zip files for simple upload code. (the only code is on AddDatabse, other fragment or activity is just autogenerated by android studio by when i create new project with slider theme)
How i get the error still the same,
1. press floating "email" button to go to fragment add databse
2. fill the textbox and choose image
3. press "Add New Item" button
4. error appears
FYI i'm using android studio 3.2 canary 12
Sometimes i event cannot go to AddDatabse fragment, the emulator just restart, eventhough i can fo to gallery fragment just fine.
Or That should not be the case?
If it not then i will make another thread for it, as for standalone project here is the zip files for simple upload code. (the only code is on AddDatabse, other fragment or activity is just autogenerated by android studio by when i create new project with slider theme)
How i get the error still the same,
1. press floating "email" button to go to fragment add databse
2. fill the textbox and choose image
3. press "Add New Item" button
4. error appears
FYI i'm using android studio 3.2 canary 12
Sometimes i event cannot go to AddDatabse fragment, the emulator just restart, eventhough i can fo to gallery fragment just fine.
ke...@google.com <ke...@google.com>
ku...@google.com <ku...@google.com> #36
Thanks for the feedback. Could you please confirm whether this is still an issue in the latest stable version of [Android Studio](https://d.android.com/studio )?
For information of what’s needed in the report please don’t forget to read this guide athttps://developer.android.com/studio/report-bugs
For information of what’s needed in the report please don’t forget to read this guide at
an...@google.com <an...@google.com> #37
Our team had requested additional information for this issue which was not provided within 30 days. Unfortunately there is not enough information for us to proceed and this issue is now closed.
In the future, if you encounter this or any other issue, please readhttps://developer.android.com/studio/report-bugs.html and file a new bug report with all the required information. This will help ensure the team can correctly triage, reproduce, and resolve your issue.
Thank you!
In the future, if you encounter this or any other issue, please read
Thank you!
Description
AI-162.4069837, JRE 1.8.0_131-b11x32 Oracle Corporation, OS Windows 7(x86) v6.1 Service Pack 1, screens 1920x1080
IMPORTANT: Please read
I have set minimum sdk to be API21 while my virtual device run on API23. I tried to save image to server and do it on asynctask. I tried to debug the code and found out that the problem is in asyncTAsk.class
public class inserttable extends AsyncTask<Void,Void,Void>{
String name, description,isiprice;
ImageView isiimage;
public inserttable(String name,String desc,String price,ImageView image) {
this.description=desc;
this.isiprice=price;
this.isiimage=image;
}
@Override
protected Void doInBackground(Void... voids) {
byte[] imgbyte=imagetobyte(isiimage);
String encodeimage= Base64.encodeToString(imgbyte,Base64.DEFAULT);
Map<String,String> datatosend=new HashMap<>();
datatosend.put("name",name);
datatosend.put("image",encodeimage);
datatosend.put("desc",description);
datatosend.put("price",isiprice);
connecttoserver(datatosend);
return null;
}
@Override
protected void onPostExecute(Void aVoid) {
super.onPostExecute(aVoid);
//kalo udah kosongin data
title.setText(""); desc.setText(""); price.setText(""); gambar.setImageResource(R.drawable.ic_menu_gallery);
}
}
and here is connecttoserver method
public void connecttoserver(Map<String,String> data){
String server="
String filename="saveimage.php";
String encodeurl=encodingurl(data); //ini buat tambahi post di url e
BufferedReader reader=null;
try {
URL url=new URL(server+filename);
HttpURLConnection connection=(HttpURLConnection) url.openConnection();
connection.setRequestMethod("POST");
connection.setDoOutput(true);
OutputStreamWriter writer=new OutputStreamWriter(connection.getOutputStream());
writer.write(encodeurl);
writer.flush();
StringBuilder sb=new StringBuilder();
reader=new BufferedReader(new InputStreamReader(connection.getInputStream()));
String line;
while ((line=reader.readLine())!=null){
sb.append(line+"\n");
}
//Just check to the values received in Logcat
Log.i("custom_check","The values received in the store part are as follows:");
Log.i("custom_check",sb.toString());
Toast.makeText(getContext(), "Upload Data Suceed ", Toast.LENGTH_LONG).show();
} catch (IOException e) {
//e.printStackTrace();
Log.i("error koneksi: ",e.getMessage());
}
finnaly{
try {
reader.close();
} catch (IOException e) {
Log.i("error close reader: ",e.getMessage());
}
} <-- from here f8 key moved me to asyncTask.class
}
The image uploaded with no error or warning, yet when I press F8 after connect to server method it moved me to asnycTask.class with error "source code does not match byte code"
Here is the picture error on asyncTask.class
When i presss f9 the emulator said the apps is stopped(the apps never got to postexecute).
I try to search for possible solution, some says it's IDEA bug some says i need to uninstall, clean and rebuild project, disable instant run, invalidate caches and restart.
I have tried it all with no result.