LOL 
1 Like
I’m reopening this topic because I’ve noted that this is a Kodular bug indeed.
I know that now because I’m using the same method but using now the PicToDrive extension (Pictodrive Extension | By Ct tricks & Techy Bro) and it still uploading the same image.
The blocks can’t distinguish this ImgLogoOficina.Picture 
from this ImgFotoUser.Picture 
View from Drive:
1 Like
I really would appreciate if somebody could gimme a hand on it, my development it’s stuck at this bug.
because you do not provide a aia test, by reproducing the problem, it is easier for the community to help
I can’t do that because this is a private project, but the relevant blocks to reproduce the issue are attached.
(It’s very unusual to ask aia to give any support)
Is this what you’re looking for, perhaps?
Not at all Vishwas…
The first Picture it’s a Logo and the second Picture it’s a User Photo, they are different pictures and they are displayed at each Image component.
When I click save button it sends those Pictures to the cloud, I’ve tried Firebase and Google Drive so far, but somehow, Kodular can’t distinguish this “.Picture” 
from this “.Picture” 
I can’t explain better than this 
use Do it to debug your blocks and provide another screenshot including Do it results
see tip4 about how to use Do it App Inventor: How to Learn | Pura Vida Apps
Taifun
2 Likes
There is no way for us to validate that ImgLogoOficina.Picture and ImgFotoUser.Picture are indeed different. Where do those pictures come from? What is the process that actually populated the content and assigned the image to those variables?
At this point, insisting that there is a bug but not showing whatever other blocks there are that may access or assign a value to those variables – let alone the entirety of the code including the interface – is akin to calling a doctor and stating that you are sick, but refusing to show up at the medical clinic for examination.
If you consider your project private, haw about you make a different project, one that is much more limited in scope – that is, one that ONLY access and process those images, but still displays the “bug” – and sharing that instead, so we at least have something to look at?
3 Likes
This is probably the most important - and unfortunately ignored - advice to find issues, mistakes and solutions.
I really don’t know how often Taifun has already given this advice here or in the AI2 forum.
4 Likes
Test.aia (77.0 KB)
Just fill the Pictoimage Folder ID as the instructions on this link (Pictodrive Extension | By Ct tricks & Techy Bro), this aia is reproducing the error exactly as my project.
Companion can’t perform decent tests, Mika himself recommend to use emulators instead.
It’s painfull to have one app in my phone to perform just one “do it” in my blocks.
Connection via USB it’s off the table I guess, never managed to make it work (yes, I’ve followed all the tutorials)…
???
are you saying, you prefer to NOT use the debugging feature? how do you find your bugs? by asking in the forum?
exactly
Taifun
2 Likes
Yes, like almost everybody in this community.
I’ve just posted the aia file and we are still discussing it?
I’ll debug it with companion, just can’t do it now because the web I’m connected blocks the companion protocols.
Because you are using the same image
1 Like
I fail to follow your logic.
Presumably, you click on the “Photo” button, which launches the PICK activity, where you select an image.
After that activity has completed, it returns, triggering the “After Activity” event where you use the URI of the image (why use “Activity_Starter1.Result URI” instead of “result”; does Image Editor ask for an image or the URI of an image?) to crop/resize/whatever and push the image in “Photo.Picture”.
Then what?
You click on the “Save”, which is supposed to take the image of the LOGO (i.e. NOT the Photo; at this point, it is assumed that LOGO has not been activated) and save it by calling Pictodrive1, which will, when completed, trip the Pictodrive1.UploadSuccess event, which will launch ANOTHER instance of Pictodrive1, this time with the Photo component, which will, when completed, trip the Pictodrive1.UploadSuccess event, which will launch YET ANOTHER instance of Pictodrive1 (with Photo) which will therefore keep calling itself for the rest of eternity?
It worked, but I don’t noticed the changes you made in the blocks. Can you explain?
You mean you missed the “Global OneTime” that prevents the component from calling itself?
Of course, in a production app, you’d want the logic to manage the value of OneTime perhaps in a different way.
==> see how much easier it is for us to help you when you actually show some code instead of relying on our mind reading capability? 
2 Likes
only those have to ask here in the community, who are not aware, that the Do it debugging feature exists…
usually a developer does the work himself/herself rather than ask others to debug the project… also doing it yourself would be much faster but it seems to be you have loads of time…
Taifun
2 Likes