Nuke | A collection of scripts and tools

As per the comments I poked around in this a little and was about to open an issue or ask colleagues when I suddenly realized: maybe this is just a debug thing.

When you put a debug build on your device and hit "Delete Data" on your app it stops working. What triggered me was that the data also was pretty big to begin with (60mb for a File > New Project app).

When you switch to a release build, the size decreases drastically and also this problem then goes away. I haven't checked, but my assumption is that we add files to our app data for debugging purposes that are removed by hitting "Delete Data" however, an app in release build (and thus apps that you distribute) are not affected.

For completeness, this isn't just affecting .NET MAUI Blazor apps but also .NET MAUI apps, Xamarin.Android apps and Xamarin.Forms apps.

I found out the solution for the Discord Button Interaction.

In this part of code:

There might be different settings of your PHP environment used in Command Line Interpreter/Interface CLI vs Common Gateway Interface CGI .

First compare what .ini files are loaded in both environment, ie.

1. for CLI run php -i
2. for CGI create a file phpinfo.php with only content and open it in the web browser.

It seems native-base searches "react-dom": "*" and could not find it so somehow uses "react-dom": "17.0.2" and it in turn looks for "react": "17.0.2" which conflicts with expo's "react": "17.0.1".

So adding "react-dom": "17.0.1" as dependency solved the problem. By this way "react-dom": "*" finds "react-dom": "17.0.1" which is dependent to Expo's version "react": "17.0.1". (Please let me know if this conclusion is wrong.)

Following are the ones related with native-base and these versions should be used otherwise the npm install fails for Expo 44:

I have to set process tool path. I fixed it by adding the path of MSBuild.exe

From what you're saying, it sounds like you have migration files that are out of wack and you're constantly running into issues relating to database migrations. I would recommend you just remove all of your migration files and start with a new initial migration after you make all the necessary model changes and restructuring of the schema.

When it comes time to make the migration on your production server, it might make the most sense to --fake-initial and manually making the database changes outside of Django so it matches your schema.

I might get a lot of backlash about this and obviously use your best judgement, but from my experience it was much easier to go about this problem this way and not wasting time making custom migration files that try to fix all of your problems.

Time and time again, when I try to migrate the table on production, I get a litany of errors.

I highly recommend you take the time to get acquainted with how to make migrations by reading the official Django docs, you will save yourself a LOT of headache.

... each time I attempt major migrations on production I end up needing to use the nuclear option - delete all migrations

You shouldn't be deleting your migration files every time there's an issue.

Are migrations even supposed to be committed?

You should definitely be committing your migrations. If you're working on a team, they would be using the migration files you created to make the necessary changes on their local DB as well as any dev/prod server you may have.

if you want to add any new fields to your models make sure that you don't have any previously added records in the DB. if you have any records you should out some default values in the model field. because when you try to migrate new fields without any default value what should DB do ? how should it fill for the previous records? so there is 2 way to fix it as it says:

1. Provide a one-off default now (will be set on all existing rows with a null value for this column)
2. Quit and manually define a default value in models.py.

so you can select option 1 and write a python command to fill the previous records or select option 2 and define the default value in the model field manually

You can start with something like this:

Try: