Highlighted

[Android] Read "position" property of the async opened FileStream after writing data from Socket cause application crash

Engaged ,
May 06, 2015

Copy link to clipboard

Copied

Here is the bugbase ticked: Bug#3982883 - [Android] Read "position" property of the async opened FileStream after writing data f...

Read "position" property of the async opened FileStream after writing data from Socket cause application crash.

It has been tested with AIR 14.0.0.178, AIR 16, AIR 17.0.0.144 and AIR 18.0.0.109 beta with Android 4.4.2 and Android 5.0.2 with different devices. Same problem in all cases. That works fine with Windows.

Steps to Reproduce:

1) Open file for writing via openAsync method.

2) Receive data from socket connection (as a client via Socket ProgressEvent.SOCKET_DATA event) and read it to temp ByteArray.

3) Write temp ByteArray to opened file.

4) Read FileStream "position" property (trace it, for example). There will be application crash.

I'd like to ask everyone affected by this issue to take a minute and vote for the following bug.

Thanks.

TOPICS
Performance issues

Views

1.1K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

[Android] Read "position" property of the async opened FileStream after writing data from Socket cause application crash

Engaged ,
May 06, 2015

Copy link to clipboard

Copied

Here is the bugbase ticked: Bug#3982883 - [Android] Read "position" property of the async opened FileStream after writing data f...

Read "position" property of the async opened FileStream after writing data from Socket cause application crash.

It has been tested with AIR 14.0.0.178, AIR 16, AIR 17.0.0.144 and AIR 18.0.0.109 beta with Android 4.4.2 and Android 5.0.2 with different devices. Same problem in all cases. That works fine with Windows.

Steps to Reproduce:

1) Open file for writing via openAsync method.

2) Receive data from socket connection (as a client via Socket ProgressEvent.SOCKET_DATA event) and read it to temp ByteArray.

3) Write temp ByteArray to opened file.

4) Read FileStream "position" property (trace it, for example). There will be application crash.

I'd like to ask everyone affected by this issue to take a minute and vote for the following bug.

Thanks.

TOPICS
Performance issues

Views

1.1K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
May 06, 2015 0
Engaged ,
May 31, 2015

Copy link to clipboard

Copied

The same problem if you try to call addEventListener or close methods instead of read FileStream position.
So, async opened FileStream with writing bytes from Socket completely unusable with Android.
Please fix it ASAP.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
May 31, 2015 0
Engaged ,
Feb 28, 2016

Copy link to clipboard

Copied

Problem still exists with AIR 21.0.0.128 beta.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 28, 2016 0
Adobe Employee ,
Feb 29, 2016

Copy link to clipboard

Copied

I'm asking the team to take a look, does this still occur with the 21.0.0.150 beta?

Thanks,
Chris

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 29, 2016 0
Engaged ,
Mar 01, 2016

Copy link to clipboard

Copied

Hi, Chris.

It works a little bit better with latest AIR 21.0.0.150 beta, but it still crashes.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 01, 2016 0
Adobe Employee ,
Mar 01, 2016

Copy link to clipboard

Copied

Thank you for checking.  Our QA team has investigated and they were also able to reproduce.  We'll continue to work on this and keep the bug updated.

Chris

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 01, 2016 0
Engaged ,
Mar 16, 2017

Copy link to clipboard

Copied

Hi, Chris

Bug still exists with latest AIR 25.0.0.134.

https://tracker.adobe.com/#/view/AIR-3982883

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 16, 2017 0
Engaged ,
Jun 13, 2018

Copy link to clipboard

Copied

This issue still exists with latest AIR 30.0.0.107.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jun 13, 2018 0
itlancer LATEST
Engaged ,
Mar 02, 2020

Copy link to clipboard

Copied

With latest AIR 33.1.0.50 it works fine for Android and iOS.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Mar 02, 2020 0