Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
3.5.0
-
None
-
Nexus 5, Android 4.4.2
Description
Using different functions the same error occurs. Calling a function the first time no callbacks are being executed. There is no error in the log. Using the same function again for a second call, everything works fine. Now the first call is being executed as well and I receive the callback from the first excution.
It looks like something is wainting. It is odd that the second call works and executes the first call as well.
I found this bug on this calls:
- window.requestFileSystem(LocalFileSystem.PERSISTENT, 3097152, gotFS, fail);
- navigator.camera.getPicture(onSuccessCapturePhoto, onFailCamera,
{ targetWidth: 1200, targetHeight: 1200, quality: 55, destinationType: Camera.DestinationType.FILE_URI, saveToPhotoAlbum: true, correctOrientation:true}
);
- navigator.camera.getPicture(onSuccessGetPhoto, onFailCamera,
{ targetWidth: 1000,targetHeight: 1000, quality: 65, destinationType: Camera.DestinationType.FILE_URI , saveToPhotoAlbum: false , sourceType: Camera.PictureSourceType.SAVEDPHOTOALBUM, correctOrientation:true}
);
Attachments
Attachments
Issue Links
- is duplicated by
-
CB-7104 Plugin results not transmitted back to devices (specially Samsung S4 and S5)
- Closed
-
CB-6984 requestFileSystem does not always return after document reload
- Closed
-
CB-7032 File Transfer upload fails to fire success function on Android
- Closed
-
CB-7439 Android Javascript androidExec online events callback messages delayed
- Closed
-
CB-7855 FileTranswer.download doesn't always call successCallback directly
- Closed
-
CB-7886 window.location.href causes a delay in the notification.confirm callback [multiple pages project]
- Closed
- is related to
-
CB-6047 File plugin callback problem with android 4.4 kitkat
- Closed
- relates to
-
CB-6667 window.requestFileSystem - callbacks are not fired in a particular circumstance
- Closed