-
Notifications
You must be signed in to change notification settings - Fork 578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.lang.NumberFormatException: For input string: "" #3864
Labels
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
kabeer-uber
added a commit
to kabeer-uber/firebase-android-sdk
that referenced
this issue
Jul 1, 2022
…le path As the issue firebase#3864 details, this is an edge case I would like to fix and shouldn't occur in regular occurrence. An alternative to this fix is to potentiall change CUSTOM_MODEL_ROOT_PATH = "com.google.firebase.ml.custom.models"; to something different than what FirebaseModelManager was using.
kabeer-uber
added a commit
to kabeer-uber/firebase-android-sdk
that referenced
this issue
Jul 1, 2022
…le path As the issue firebase#3864 details, this is an edge case I would like to fix and shouldn't occur in regular occurrence. An alternative to this fix is to potentiall change CUSTOM_MODEL_ROOT_PATH = "com.google.firebase.ml.custom.models"; to something different than what FirebaseModelManager was using.
Hi @kabeer-uber, thanks for reporting and creating a pull request! I'll let our engineers check and see if it's clear to merge or if changes have to be made. |
kabeer-uber
added a commit
to kabeer-uber/firebase-android-sdk
that referenced
this issue
Jul 6, 2022
…le path As the issue firebase#3864 details, this is an edge case I would like to fix and shouldn't occur in regular occurrence. An alternative to this fix is to potentiall change CUSTOM_MODEL_ROOT_PATH = "com.google.firebase.ml.custom.models"; to something different than what FirebaseModelManager was using.
rlazo
pushed a commit
that referenced
this issue
Jul 6, 2022
…le path (#3865) As the issue #3864 details, this is an edge case I would like to fix and shouldn't occur in regular occurrence. An alternative to this fix is to potentiall change CUSTOM_MODEL_ROOT_PATH = "com.google.firebase.ml.custom.models"; to something different than what FirebaseModelManager was using.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
[READ] Step 1: Are you in the right place?
Yes
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
Note this is an edge case the requirement to hit this edge case are as below:
Be in the process of migrating from FirebaseModelManager (old version) to FirebaseModelDownloader (open source).
Why because they store the same model in the exact same destination. Path (/data/user/0/<app package name>/no_backup/com.google.firebase.ml.custom.models/<firebase persistent key>/<model name>) verified by checking the file paths via both the downloaders. But they store model details in different locations, i.e details in the SharedPreferences cache are in different namespaces. (Open source firebase model downloader stores it in com.google.firebase.ml.modelDownloader and likely old FirebaseModelManager stores it here com.google.firebase.ml.common.modeldownload)
Two models need to be triggered for download at the same time (It leads to partial information present in the SharedPreferences cache) and with the larger model already downloaded on the device. Smaller model download = faster download time relative to larger model download.
Why because when the smaller model completes downloading and the larger model is in progress when we look to clean up files post smaller model download, we find the larger model folder but do not find the larger model file path in the SharedPreferences cache (although the file is on the device). Thus we get an empty file path for the larger model resulting in the below stack trace.
We would not see this issue:
Relevant Code:
The text was updated successfully, but these errors were encountered: