Number format exception Transfer Record #1461

sougandhmp · 2020-01-30T15:53:34Z

Sharing the crash logs

AWS s3 transfer utility causes crash. Have seen similar bug
#1093 in which it was suggested to remove "awss3transfertable.db"which i have not tried. But I have tried updating to the latest version but still issues are reported..

Caused by java.lang.NumberFormatException
For input string: "ANY"

sun.misc.FloatingDecimal.readJavaFormatString (FloatingDecimal.java:2043)
sun.misc.FloatingDecimal.parseDouble (FloatingDecimal.java:110)
java.lang.Double.parseDouble (Double.java:538)
com.google.gson.stream.JsonReader.nextInt (JsonReader.java:186)
com.google.gson.internal.bind.TypeAdapters$7.a (TypeAdapters.java:13)
com.google.gson.internal.bind.TypeAdapters$7.read (TypeAdapters.java)
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.a (ReflectiveTypeAdapterFactory.java:2)
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.a (ReflectiveTypeAdapterFactory.java:47)
com.google.gson.Gson.a (Gson.java:20)
com.google.gson.Gson.a (Gson.java:4)
com.google.gson.Gson.a (Gson.java:9)
com.google.gson.Gson.assertFullConsumption (Gson.java)

com.amazonaws.mobileconnectors.s3.transferutility.TransferRecord.a (TransferRecord.java:422)
com.amazonaws.mobileconnectors.s3.transferutility.TransferDBUtil.getTransferById (TransferDBUtil.java:16)
com.amazonaws.mobileconnectors.s3.transferutility.TransferUtility.a (TransferUtility.java:20)
com.amazonaws.mobileconnectors.s3.transferutility.TransferUtility.a (TransferUtility.java:2)
com.amazonaws.mobileconnectors.s3.transferutility.TransferUtility.a (TransferUtility.java:23)

AWS Android SDK Version: [e.g. 2.16.6, older versions also]
Device: [e.g. Galaxy S9 and many devices]
Android Version: [9]

raphkim · 2020-01-31T18:33:00Z

Hi @sougandhmp ,

There may be a potential issue with how GSON de/serializes TransferNetworkConnectionType in the Android SDK for S3 when the code is obfuscated. Would you be able to try modifying your proguard configuration as following?

sougandhmp · 2020-02-02T23:00:02Z

Hi @raphkim,
Thanks for the suggestion, I have added -keepclassmembers enum * { *; } to the proguard rules. I will be checking crash is happening again for this reason.

sougandhmp · 2020-02-10T10:04:04Z

Hi @raphkim ,

Is there something that can be done, other than adding "-keepclassmembers enum * { *; } " to pro-guard rules?.Please note the issue was not reported for fresh users. Further more, the issue seems to recur for specific users.

Any help would be appreciated.

raphkim · 2020-02-12T00:33:48Z

Have you tried deleting "awss3transfertable.db"? If the issue is only recurring for some people, I think it may be possible for the database to be corrupted.

sougandhmp · 2020-02-17T15:02:57Z

Hi @raphkim , @palpatim

I have not tried deleting "awss3transfertable.db". I have already mentioned it in the description of bug.
Since the issue was only happening for few production users i was not able to reproduce and check the issue.

raphkim · 2020-02-19T17:48:07Z

I would suggest clearing the transfer database before moving forward. Once the database is corrupted, the issue will persist as long as the app continues to access it.

svanegas · 2020-03-02T17:14:37Z

@sougandhmp, did you try deleting the "awss3transfertable.db"? any updates on your end?

@raphkim. I'm having the same issue and I'm not using obfuscation. Here's the stacktrace:

Caused by java.lang.NumberFormatException: Invalid double: "ANY"
       at java.lang.StringToReal.invalidReal(StringToReal.java:63)
       at java.lang.StringToReal.initialParse(StringToReal.java:164)
       at java.lang.StringToReal.parseDouble(StringToReal.java:282)
       at java.lang.Double.parseDouble(Double.java:301)
       at com.google.gson.stream.JsonReader.nextInt(JsonReader.java:1201)
       at com.google.gson.internal.bind.TypeAdapters$7.read(TypeAdapters.java:226)
       at com.google.gson.internal.bind.TypeAdapters$7.read(TypeAdapters.java:218)
       at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:131)
       at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:222)
       at com.google.gson.Gson.fromJson(Gson.java:927)
       at com.google.gson.Gson.fromJson(Gson.java:892)
       at com.google.gson.Gson.fromJson(Gson.java:841)
       at com.google.gson.Gson.fromJson(Gson.java:813)
       at com.amazonaws.mobileconnectors.s3.transferutility.TransferRecord.updateFromDB(TransferRecord.java:159)
       at com.amazonaws.mobileconnectors.s3.transferutility.TransferDBUtil.getTransferById(TransferDBUtil.java:865)
       at com.amazonaws.mobileconnectors.s3.transferutility.TransferUtility.submitTransferJob(TransferUtility.java:901)
       at com.amazonaws.mobileconnectors.s3.transferutility.TransferUtility.pause(TransferUtility.java:772)
       at com.amazonaws.mobileconnectors.s3.transferutility.TransferUtility.pauseAllWithType(TransferUtility.java:787)

SDK Version: 2.16.5
Noticed that happens mostly on Samsung devices with Android 10

Since I can't reproduce either, do you have some idea how this can be reproducible? Furthermore, about deleting the "awss3transfertable.db":

Could you please specify how should this process be done?
When exactly needs to be deleted?
Wouldn't it affect anything else in the schema?

Thanks

sougandhmp · 2020-03-04T23:21:15Z

Hi @svanegas,

No I couldn't verify the solution since I was not able to reproduce the crash.

svanegas · 2020-04-15T15:15:38Z

@TrekSoft, @desokroshan, @palpatim, @raphkim. Guys, I'm still facing this issue and it's becoming now a big deal in production. Could anyone please assign to corresponding person and reopen this ticket?

Stack trace is above, and as I mentioned, occurs mostly on Samsung devices with Android 10.

Could you please explain me how could I implement a workaround or solve this issue?

Thanks

raphkim · 2020-04-15T18:17:29Z

Hi @svanegas ,

I apologize for pre-maturely closing the issue. It seems to me that most people that have experienced this issue were able to resolve their issue by deleting their in-memory transfer data "awss3transfertable.db". This is the database that stores all of the ongoing transfers in the app so that the information is not lost upon closing the app.

This database can be deleted by using Context#deleteDatabase(String) method and using "awss3transfertable.db" as the argument. However, I would advise against using this regularly inside the app outside of the context of explicitly clearing data.

I will further investigate the issue to see what we can do to mitigate the corruption of database.

raphkim · 2020-04-15T18:19:20Z

@svanegas would you be able to check if you have minifyEnabled set to true inside your build.gradle file?

svanegas · 2020-04-15T18:51:55Z

@raphkim. Thank you for reply.

Yes, minifyEnabled is true.

I was getting ready to release soon a prod version that uses deleteDatabase("awss3transfertable.db") in the onCreate() of the Application class as a temporary workaround. But then I saw that you advise against using it this way.

Do you think the deletion of the database every time app is opened would affect something else? What do you think could be done better?

raphkim · 2020-04-15T19:46:04Z

For future reference, minifyEnabled = true will obfuscate your code ;)

Deleting the database in the onCreate() method would remove the transfer information every time the app is exited, which defeats the purpose of keeping a persistent record of the ongoing transfers. This issue should ideally be resolved once the corrupted table is deleted once (outside of the app's lifecycle), and should not require it to be deleted thereafter.

svanegas · 2020-04-15T19:51:44Z

For future reference, minifyEnabled = true will obfuscate your code ;)

Deleting the database in the onCreate() method would remove the transfer information every time the app is exited, which defeats the purpose of keeping a persistent record of the ongoing transfers. This issue should ideally be resolved once the corrupted table is deleted once (outside of the app's lifecycle), and should not require it to be deleted thereafter.

@raphkim. Okay, so do you think a good strategy would be: Catch this exception, when this happens, delete database. It might be enough, right?

raphkim · 2020-04-16T17:07:41Z

There may be a potential issue with how GSON de/serializes TransferNetworkConnectionType in the Android SDK for S3 when the code is obfuscated. Would you be able to try modifying your proguard configuration as following?

While deleting database upon gson failure would be a good temporary workaround, I suggest that you verify the above solution first for a more permanent solution. With the temporary solution you've provided, a user experiencing this issue will inexplicably lose data on all of the ongoing/past transfers

svanegas · 2020-04-16T18:10:36Z

Thanks @raphkim.

I already had this config, actually:

-keepnames class com.amazonaws.**
-keepnames class com.amazon.**

We will see how it behaves with database deletion workaround!

raphkim · 2020-04-16T18:13:48Z

Here is the full config that you should use when enabling proguard:
https://github.com/aws-amplify/aws-sdk-android/blob/master/Proguard.md

Also -keepclassmembers enum * { *; } would be the required config to resolve this particular issue.

buntupana · 2022-11-03T19:29:16Z

After more than two year this issue is still happening sometimes. Is there any solution to prevent this happening?

AnupPorter · 2022-12-08T09:27:44Z

@raphkim
How is the database getting corrupt in the first place? This might happen again in the future, and I need to identify it.

PruthvirajSoftvan · 2022-12-13T05:50:13Z

I have faced an issue after updating aws SDK from 2.28.0 to 2.58.0

Fatal Exception: com.google.gson.n: java.lang.NumberFormatException: For input string: "ANY"
       at com.google.gson.internal.bind.TypeAdapters$7.b(TypeAdapters.java:25)
       at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:2)
       at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:47)
       at com.google.gson.Gson.fromJson(Gson.java:31)
       at com.google.gson.Gson.b(Gson.java:1)
       at com.amazonaws.mobileconnectors.s3.transferutility.TransferRecord.updateFromDB(TransferRecord.java:422)
       at com.amazonaws.mobileconnectors.s3.transferutility.TransferNetworkLossHandler.resumeAllTransfersOnNetworkAvailability(TransferNetworkLossHandler.java:73)
       at com.amazonaws.mobileconnectors.s3.transferutility.TransferNetworkLossHandler$1.run(TransferNetworkLossHandler.java:73)
       at java.lang.Thread.run(Thread.java:1012)

Update Aws SDK from 2.28.0 to 2.58.0
Also added poguard rules which is already disccus in above conversation but still issue was show in firabse crashlytics.

Refer to above conversation and following steps deleted by using Context#deleteDatabase(String) method so my question is that affect any other schema or internal app database or any change to crash end user or client app at production?

mquineche · 2023-02-02T17:16:19Z

I'm facing this issue.
I updated AWS SDK from 2.13.7 to 2.62.2.
From Crashltycs: 5k crash events in 5 users

Fatal Exception: com.google.gson.JsonSyntaxException: java.lang.NumberFormatException: For input string: "ANY" at com.google.gson.internal.bind.TypeAdapters$11.read(TypeAdapters.java:307) at com.google.gson.internal.bind.TypeAdapters$11.read(TypeAdapters.java:297) at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:131) at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:222) at com.google.gson.Gson.fromJson(Gson.java:963) at com.google.gson.Gson.fromJson(Gson.java:928) at com.google.gson.Gson.fromJson(Gson.java:877) at com.google.gson.Gson.fromJson(Gson.java:848) at com.amazonaws.mobileconnectors.s3.transferutility.TransferRecord.updateFromDB(TransferRecord.java:159) at com.amazonaws.mobileconnectors.s3.transferutility.TransferNetworkLossHandler.resumeAllTransfersOnNetworkAvailability(TransferNetworkLossHandler.java:176) at com.amazonaws.mobileconnectors.s3.transferutility.TransferNetworkLossHandler.access$000(TransferNetworkLossHandler.java:37) at com.amazonaws.mobileconnectors.s3.transferutility.TransferNetworkLossHandler$1.run(TransferNetworkLossHandler.java:123) at java.lang.Thread.run(Thread.java:919)

So any of those workaround has fixed this particular issue ?

buntupana · 2023-03-09T05:56:34Z

And still no official answer

buntupana · 2023-04-07T14:47:22Z

@raphkim I'm still experiencing this issue once in a while for some production users and I can't even catch it to avoid crash and delete the database as it's suggested so I have no real solution.

sdhuka · 2023-04-07T14:52:08Z

@buntupana We have reopened the issue and investigate further.

sdhuka · 2023-06-20T16:45:44Z

@buntupana We have added the fix to prevent the crash in case of deserialization exception. Please update to the latest sdk version for the fix.

raphkim added bug Something isn't working s3 Issues with the AWS Android SDK for Simple Storage Service (S3). labels Jan 31, 2020

raphkim self-assigned this Jan 31, 2020

raphkim added the closing soon Issue will auto-close if there is no additional activity within 7 days. label Feb 7, 2020

stale bot removed the closing soon Issue will auto-close if there is no additional activity within 7 days. label Feb 10, 2020

palpatim added the pending-community-response Issue is pending response from the issue requestor label Feb 14, 2020

TrekSoft unassigned raphkim Mar 27, 2020

desokroshan added the closing soon Issue will auto-close if there is no additional activity within 7 days. label Apr 3, 2020

desokroshan closed this as completed Apr 3, 2020

raphkim reopened this Apr 15, 2020

stale bot removed the closing soon Issue will auto-close if there is no additional activity within 7 days. label Apr 15, 2020

raphkim self-assigned this Apr 16, 2020

raphkim closed this as completed Apr 16, 2020

raphkim mentioned this issue Oct 5, 2020

Question: How to migrate to v2.19.0 from v2.9.0 ? #2141

Closed

sdhuka reopened this Apr 7, 2023

sdhuka assigned sdhuka and unassigned raphkim Apr 7, 2023

sdhuka mentioned this issue May 19, 2023

fix(storage): set transferUtilitOptions to default incase of deserialization e… #3296

Merged

sdhuka closed this as completed Jun 20, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Number format exception Transfer Record #1461

Number format exception Transfer Record #1461

sougandhmp commented Jan 30, 2020 •

edited

Loading

raphkim commented Jan 31, 2020

sougandhmp commented Feb 2, 2020

sougandhmp commented Feb 10, 2020 •

edited

Loading

raphkim commented Feb 12, 2020

sougandhmp commented Feb 17, 2020

raphkim commented Feb 19, 2020

svanegas commented Mar 2, 2020 •

edited

Loading

sougandhmp commented Mar 4, 2020

svanegas commented Apr 15, 2020 •

edited

Loading

raphkim commented Apr 15, 2020

raphkim commented Apr 15, 2020

svanegas commented Apr 15, 2020

raphkim commented Apr 15, 2020

svanegas commented Apr 15, 2020

raphkim commented Apr 16, 2020

svanegas commented Apr 16, 2020 •

edited

Loading

raphkim commented Apr 16, 2020

buntupana commented Nov 3, 2022 •

edited

Loading

AnupPorter commented Dec 8, 2022 •

edited

Loading

PruthvirajSoftvan commented Dec 13, 2022 •

edited

Loading

mquineche commented Feb 2, 2023

buntupana commented Mar 9, 2023

buntupana commented Apr 7, 2023 •

edited

Loading

sdhuka commented Apr 7, 2023

sdhuka commented Jun 20, 2023

Number format exception Transfer Record #1461

Number format exception Transfer Record #1461

Comments

sougandhmp commented Jan 30, 2020 • edited Loading

raphkim commented Jan 31, 2020

sougandhmp commented Feb 2, 2020

sougandhmp commented Feb 10, 2020 • edited Loading

raphkim commented Feb 12, 2020

sougandhmp commented Feb 17, 2020

raphkim commented Feb 19, 2020

svanegas commented Mar 2, 2020 • edited Loading

sougandhmp commented Mar 4, 2020

svanegas commented Apr 15, 2020 • edited Loading

raphkim commented Apr 15, 2020

raphkim commented Apr 15, 2020

svanegas commented Apr 15, 2020

raphkim commented Apr 15, 2020

svanegas commented Apr 15, 2020

raphkim commented Apr 16, 2020

svanegas commented Apr 16, 2020 • edited Loading

raphkim commented Apr 16, 2020

buntupana commented Nov 3, 2022 • edited Loading

AnupPorter commented Dec 8, 2022 • edited Loading

PruthvirajSoftvan commented Dec 13, 2022 • edited Loading

mquineche commented Feb 2, 2023

buntupana commented Mar 9, 2023

buntupana commented Apr 7, 2023 • edited Loading

sdhuka commented Apr 7, 2023

sdhuka commented Jun 20, 2023

sougandhmp commented Jan 30, 2020 •

edited

Loading

sougandhmp commented Feb 10, 2020 •

edited

Loading

svanegas commented Mar 2, 2020 •

edited

Loading

svanegas commented Apr 15, 2020 •

edited

Loading

svanegas commented Apr 16, 2020 •

edited

Loading

buntupana commented Nov 3, 2022 •

edited

Loading

AnupPorter commented Dec 8, 2022 •

edited

Loading

PruthvirajSoftvan commented Dec 13, 2022 •

edited

Loading

buntupana commented Apr 7, 2023 •

edited

Loading