-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Response property doesn't exist on FileUploadResult. #1002
Comments
Hi guys! It happens to me right now and I already deleted node_modules and do Cordova CLI: 6.4.0 |
@ihadeed Since you closed this is it going to be released? |
I have the same error |
@sjosen Until he releases the commit you would need to go back to |
I have the same error with ionic-native": 2.4.1, Please when will be ready this release? |
@betollaque you would need to change your ionic native version to "ionic-native": "2.2.11". |
@betollaque I solved by applying the fix manually. Not the best solution but it does the job until the new release are out. |
Thanks guys for help. @phoenixtrigo I found 2 files in my ionic project:
Both files have this line: Here I'm little confuse, could you indicate what file and line did you fix? |
@betollaque remove |
Is working! thanks! |
@betollaque glad to hear it's working now. I think the file depends on the target you have configured on the tsconfig.ts file. then it's just like @ihadeed said, remove the |
Error
Property 'response' does not exist on type 'FileUploadResult | FileTransferError'.
I was on
"ionic-native": "^2.2.11"
but I upgraded to"ionic-native": "^2.4.1",
Looks like the error is happening on this commit:
1976c38#diff-2f9b79bc9c725972a5f02017d72a1e66R226
Steps to resolve error
I did delete the node_modules & reinstall everything.
Looked for the the
response
https://github.com/driftyco/ionic-native/blob/master/src/plugins/filetransfer.ts#L66Versions
Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.0.0
The text was updated successfully, but these errors were encountered: