Unless the extensions are missing, your screenshot is showing extension conflict.
Extensions are like credit cards.
Eventually, Google will raise the SDK level or Oracle will raise the JDK level, and the bills will come due.
2 Likes
Correct, But you tell me problem not its solution, provide me solutions as a doctor at app inventor.
All you can do is to remove extensions one by one, and test compile each time, until you hopefully find the one causing the problem.
Or as I recommended in the first place. Start from scratch with AI2, so that you know where you are. You will probably do a better job of your blocks coding next time around.
See how far you can get without extensions...
1 Like
You have changed a few things since my last action, nevertheless here you go KinnkoMultiFun3.aia (485.0 KB)
P.S. Please don't ask what I did
Okay Okay, I am not asking what you have done, but I have right to ask what i have done wrong so that these errors are occurs, Provide information in Right To Information to prevent my future mistakes......
By The Way it is also not working after your fix,
Also anyone in the community are free to work and help me onto this project, I trust you all
Try to fix this below aia file
KinnkoMultiFun.aia (392.8 KB)
Also App is showing this below problem on time of installing :
Not so strange at all since it's not even the same file that I fixed for you last time.
These all are the same but I changed the name everytime to get it in the inventor, and If i edit anything in the app it shows errors. Which I am not able to fix.
I gave new aia file above, fix errors and icons errors are fixed only Not installing errors and Barcode or any component error are not fixed yet.....
https://community.appinventor.mit.edu/uploads/short-url/9zA3N3rnDUr7KBCOIcILNnV7afq.aia
@Boban help me with above aia file.
As Tim has said, it would be better to start again from scratch in App Inventor only and avoid using so many extensions.
1 Like
The whole errors are removed after the @Boban fixation. But I don't know what happens to it and it started erroring again.
There is possibly some corruption within the back files (the files that support the .aia). It is very difficult to ensure that a corrupted file is 100% clean. In the time already taken up trying to fix your files, a new one started from scratch could be well on it's way.
There is a common saying from many years ago. It is not meant to be rude or insult, but to get an important message across.
KISS:
1 Like
I agree with your KISS but, I am wondering for any solution, if I don't get fix them I want solution for transfer blocks and designs to another project easily, if that also won't work then I will think about recreations.
That would be Designer Copy/Paste, and Blocks Editor draggable downloaded png files.
We don't think well of ultimatums thank you.
If you try to use anything from your other files, behind the scenes you could be carrying across the corruption. That is why you should start again, from scratch, brand new file.
Define your App on paper first - what is the minimum functionality required?
Define snippets in App Inventor and test them. When satisfied that they work as required in all circumstances, bring them together as one file. For example, that Scan feature you added to your Project. Make a test App just for that feature to ensure you have everything just right.
"More haste, less speed." When one is in a hurry, one often ends up having less success and completing a task more slowly.
-
The app sometimes works with scan feature in companion but didn't works on installation.
-
App works in mobile but giving errors in companion.
-
App didn't works in companion and didn't installing.
-
App installed in the phone but crashing again and again.
Above circumstances happened with me again and again when I do change in @Boban's given AIA file
That brings me to another maxim:
If in doubt
rip it out
That's I am asking it again and again, How to rip that doubt?
Which is why you should start from scratch!
Ripping out extensions, procedures, and variables can be tricky in AI2.
Unlike a movie where the bad guy gets to plunge his hand into his opponent's chest and grab his heart, surgeons need to use clamps to localize their work.
(I recently had to have a shower valve replaced, and had to turn off water to the whole house because I could not locate any cut off valves for the bathroom.)
Similarly, to code for risk reduction, you would need the equivalent of those submarine doors with the big wheel, to compartmentalize your app in the case of a breach.
In the case of extensions, I would hide their use behind procedures that call them, and just call the wrapper procedures. That way, only the wrapper procedures suffer when the extension is removed.
It's better to follow the other Power Users' advice, and start fresh, only adding items that have been unit tested in various environments before a system test.