-
Notifications
You must be signed in to change notification settings - Fork 479
Invalid Path? #77
Comments
Thanks for the feedback. So we can better diagnose the issue, what version of the SDK are you using? Judging from the path, I assume you're using an emulator. Have you configured that correctly? An initial guess is that the SDK is probably writing something to the preferences, but the emulator is not happy. |
We are using the libraries in the master branch. Multi user issues I guess? But phones do not have multi user support enabled, so only /storage/emulated/legacy is available |
If you see the stack trace, you'll see there's a call from the PayPal SDK to StatFs. Perhaps we should be calling |
Same problem with the PayPalAndroidSDK, just edited the CONFIG_ENVIRONMENT to test with sandbox and the CONFIG_CLIENT_ID to match my ID.
|
I had the same issue. |
Thanks @fechy. Obviously, we shouldn't require you to add that permission to your app. We're working on getting a fix out for this issue shortly. |
Fixed in 2.4.0. |
What was the issue at the end? |
BUMP |
I apologize I am unfamiliar with the cause of this issue; however, I assume if you are seeing an invalid path error now with an updated release the cause would be different since this issue is from 2014. If you are seeing issues for Invalid Path with the most recent release could you create a new issue? |
We have been integrating the SDK into our project, it works fine in most devices expect for this one (LG Optimus 4X HD).
This is the stack trace:
Thank you
The text was updated successfully, but these errors were encountered: