I use project clean pretty much all the time.
Notes
- The ide://run method supports these additional arguments:
- FilesSync=True - Causes the IDE to sync the Files folder after operation completes.
- CleanProject=True - Causes the IDE to clean the project after operation completes.
- VMArgs - Similar to Args but added as a JVM argument.
You can add: VMArgs=-DZeroSharedFiles%3DTrue to a zipper call to delete the content of the platform specific copies of shared files (the content will be added back when the program runs, because of the custom build action).
If you really have to use Clean all of the time then you are doing something wrong. Try and fix that!
I guess eventually this option will also be available in B4A. At the moment it is announced that they will be supported on B4J and B4I.
[B4X] Comment Links
New feature added in B4A v10.0, B4J v8.50 and B4i v6.80. It will also be added to B4R. Code comments can include clickable links. The following schemes are supported: http(s):// - Link will be opened with the browser. Example: Dim key As String = OrderedMap.Keys.Get(0) 'based on...www.b4x.com
I think that you have to start by accepting that cleaning a project is not normal. If you Google for other examples of essential project cleaning these are usually cases of specific, often very large projects over which the user has lost control - they are not speaking of project cleaning "pretty much all the time".You don't get any error messages when you run an app that needs a clean, the app just doesn't run properly.
Where do you start looking for the problem?
I think that you have to start by accepting that cleaning a project is not normal. If you Google for other examples of essential project cleaning these are usually cases of specific, often very large projects over which the user has lost control - they are not speaking of project cleaning "pretty much all the time".
So stop project cleaning as a habit - instead treat the problem an intermittent bug, or maybe one of those "impossible" ones where you can see that everything is correct but still something is going wrong in execution - you don't get any compiler messages there, either. Try and separate those projects where frequent project cleaning is required with those (surely there must be some) where you do not have to clean. Where cleaning is needed, try to find some common preceding activity that might be the cause. In particular, when you work on a new project (starting a new dummy project might be a good idea) be on the lookout for the first time that you have to clean the project - what had you just done for the first time?
My concern with your wish to institutionalise project cleaning in the IDE is that this is the very opposite of my first step. Not only would that stop you ever discovering what you were doing wrong, it would prevent every other B4X user ever being aware that they had done something wrong.
That is what happens when you run in debugger mode - your app is not actually running in the device (don't ask me how this is achieved) and code changes are "instantly" applied without the need to download a replacement app. It is very quick - just what you want when debugging. You have to be a little careful if you make a coding change in initialisation code, of course, as this code might not run again when you restart.7 App started without uploading the new App code file and the debugger didn't connect over the bridge
This is also suspicious because the bridge does not disconnect in normal circumstances - something has already gone wrong.9. Pushed the compile run button - No device found
My experience:
I follow it and have no problem, as I know what to expect.
- In debug mode, if you change in designer, you need to clean project as it is not pushed to the phone.
- In release mode, if you change in designer, you do not need to clean project as new apk is pushed to the phone
Regards,
Anand
Okay - I know that you wish things were different, but here you are in a frustrating situation. I am not sure that I can help you much but here are a couple of observations from your case study above. At step 7 ...
That is what happens when you run in debugger mode - your app is not actually running in the device (don't ask me how this is achieved) and code changes are "instantly" applied without the need to download a replacement app. It is very quick - just what you want when debugging. You have to be a little careful if you make a coding change in initialisation code, of course, as this code might not run again when you restart.
Also Step 9 ...
This is also suspicious because the bridge does not disconnect in normal circumstances - something has already gone wrong.
Look - you probably have an expectation that something somewhere should happen in a certain way and are acting accordingly, but in fact your expectation is incorrect. I am afraid that I can't look at this any more at the moment. I will come back to it later in the day if I can. Good luck.
This thread is too messed up to be useful.
You don't need to clean the project in order for the layout file to be updated. This is not a common issue. Anyone who encountered such issue should start a new thread and we will further investigate it.
It sounds like the real issue is a connectivity issue. First step is to switch to USB debug mode instead of B4A-Bridge. Second step is to disable the anti virus which might be causing an issue.
This is of course the problem. Most of the other information in this thread is wrong.As for the B4A bridge dropping out, this only happens occasionally. It might be caused by my switching B4A IDE instances and forgetting to reconnect to the instance I am working on.
The only relevant information in this thread is in post #17, where you told us that you are running two IDEs connected with B4A-Bridge to the same device. Assume that everything else is wrong.What else is wrong about the information? Anything important?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?