Thank you.

I did use Capture, and then saved the file to FileSystemStorage while 
saving that path to my db so I can retrieve it later to know the paths of 
all images that were captured by the camera. 

The odd part is that the code runs fine the first time it's called. 
However, when I capture a 2nd image using the camera, calling the same code 
to store the file in FileSystemStorage, the image seems to somehow get lost 
somewhere. Is there something that changes in iOS related to file:// vs 
file:///. 

I noticed that when the image path is returned  from: 

(String) evt.getSource();

there is a different amount of "/" than when calling Are there supposed to 
be a fixed number of /'s in the path? Why would the getAppHomePath() return 
a slightly altered path from the one obtained by evt.getSource()?

Display.getInstance().getAppHomePath(); 

Could this be the issue? Why would it only manifest the 2nd time the 
Capture API is called? Is there a better way to handle images?

Thank you again.

On Monday, January 11, 2021 at 9:38:19 PM UTC-5 Shai Almog wrote:

> Hi,
> can you be more specific about the issue? Which API did you use?
>
> My guess is that you used the standard Capture API and didn't copy over 
> the image. Notice that the image generated is temporary and could be 
> overwritten by the next shot.
>
> On Monday, January 11, 2021 at 7:34:47 PM UTC+2 E wrote:
>
>> Hi, 
>>
>> I am trying to debug a problem that we have have when trying to capture 
>> an image using the camera on iOS and then display it in the Form. 
>>
>> In my case, the first time a user takes a picture, the picture is 
>> captured, stored and displays. after that, images don't seem to be properly 
>> captured and/or stored. 
>>
>> Any suggestions for debugging this, especially since it has to be built 
>> for the iOS device, which takes time (I'm not complaining)? I can place 
>> logs everywhere but what I'm asking is for any other pointers on what to 
>> look at to see where this process went wrong.   Is this the type of issue 
>> that looks like it will require debugging in Xcode to solve or are there 
>> any other options?
>>
>> Thanks!
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/08a362fb-3902-4e35-9a2c-671772017889n%40googlegroups.com.

Reply via email to