Hope you guys can help me with this weird issue I'm facing.
The app bundle is getting build everything time it finishes building. So its like once it gets to 100% it starts all over again. One thing I made to kind of solve it, is to enable the "Remote debugging" option on the expo App. But that will only work for a minute and will start the loop of building the bundle again.
I have also reinstalled the node_modules & cleaned expo cache but nothing seems to be working.
Ok, I found it. It was because of iCloud Drive on MAC. For some reason that I don't understand (since it did not happen before under the same conditions) the refresh of the files is forced.
So move your app folder to another place that is not on iCloud Drive and it will work.
Hope this will help.
It was Dropbox sync causing my issue.
Most of the time you shouldn’t need to rebuild your APK on every change, you should only need to run exp publish to see your updated app show up in your existing APK. If you change anything in app.json you’ll need to run the build again, but if you aren’t touching app.json then you should be mostly fine to just publish and not run a standalone build.
Related
Due to some reasons (I couldn't figure out why), my google default file picker has stopped working, it just crashed like end of the world.
After several attempts to fix it, i.e. clear cache & storage, force stop the app and its services, none actually helped. So I proceeded to uninstall the app updates, still, it doesn't work.
Is there anywhere I can download and update it? It ain't in Play Store.
I've got a Django site which uses the "django-machina" forum software, which in its latest incarnation apparently uses Bootstrap4 styling.
After installing the package according to directions, it looks beautiful on my development box. But, when I deploy exactly the same software on production, Bootstrap obviously isn't running because nothing is properly styled.
There are no 404's and no console messages. *(Yes, I remembered to run manage.py collectstatic ...) There are some stylesheets complaints from Firefox but they're identical in both cases. But ... the display is not!
Can anyone suggest what I might do in order to solve this problem? I'm stumped!
Well, once again I answered my own question!
I correctly guessed that, since I was maintaining the remote site from my own box using rsync, there might be some garbage left over on the remote side that wasn't being swept-up. (I can't use rsync --delete for fear of smashing directories that contain images and uploaded materials.) I guess it would probably be smarter for me to start using an external repo so that git can do for me what it's designed to do ...
But anyway, when I deleted selected directories containing the central and most-often updated directories, then used rsync to replace them with clean copies, the interference went away and production now looks correct.
I built a (relatively simple) Django project following a tutorial (the recently released Hello Web App book.) I committed my changes along each step of the way, and I have my working solution in a github repo. However, when I clone the code into a new work space such as onto a new machine or into a new slot on a cloud IDE, the app doesn't work. I get a few errors and with each I resolve, another pops up. Basically, my environment is totally messed up and incompatible with the app beyond having Python and Django both installed.
I realize that I can read through the error messages I get when I invoke runserver, solve each one by one, etc. but it seems there should be a cleaner/simpler way to be able to pull down my repo to a fresh workspace and have it up and running in just a minute or two. I've read recommendations about using virtualenv, but it also seems like people discourage including venv inside your repo because of the extraneous commits and added bulk that will result from it so I don't think that actually solves my problem of trying to reduce new workspace configuration effort.
Perhaps I am overly optimistic, but I'm hoping someone can give me a recommendation to avoid the need to workout these kinks each time I start fresh.
Title is pretty much my question. I'm serving the dist directory differently and would still like the benefit of auto-builds but I don't need to run the server. I looked in the docs and the cli help but didn't see anything specific. I know the cli help doesn't contain everything because it doesn't list ember build which is available.
If I understand correctly you are wanting the ember build command to watch for changes in the file tree and rebuild on a change?
They implemented ember build --watch a while back which will trigger when a file changes. Tested just now and it worked on 0.2.7. Not sure what version it came in though. Let me know if this is not the answer you are looking for.
I am working on an existing project that someone else started and I am having some really weird issues.
This is the rundown:
We had a cfwheels app running under test.com/admin and we wanted to make it a stand alone app to run under admin.test.com.
The developer who was in charge of the project copied the contents of the admin folder (the entire wheels app) and dumped them in a new folder. He also created a new site in IIS and mapped the physical path to run from the correct folder.
The problem now is this, when one app is running the other one is throwing an error which is telling me that the admin.test.com is pulling the contents of test.com/admin. Now if I do a reload=true and run the new application first, the new app is working and the old one is throwing an error.....
I know that this sounds a bit confusing but does anyone have an idea where to look and what I might need to change to make this issue go away?
If the application.name values are the same for both applications, then whichever runs first, configures them both.