Thanks, @maliming. This seems to solve the issue.
From my understanding looking at GitHub these fixes will be available in version 9.3, is that right? I just want to confirm that it will be safe to remove these once that version is out and we upgrade to it.
Thank you.
Hi, @maliming. I've tried doing the override you mentioned, but it doesn't seem to make a difference.
I managed to narrow it down and I've created a fresh project that reproduces the issue. You should receive the code in your email.
Here are the steps to reproduce:
Here's an image demonstrating the issue on the sample project:

Hi, @EngincanV. Any update on this?
Regarding the favicon, I managed to fix it by adding the favicon.svg file. Previously we had only a favicon.ico file.
Hi, @EngincanV thanks for the response.
I tested the change with the steps you mentioned and it did work, that is, the table created in the previous module is no longer created again in the migration for the new module.
However, I noticed that this only worked when I ran the command to remove the latest migration twice (as you instructed), and as expected that removes the last two migrations, even though the second to last migration it removes has no relation to the latest one or its tables. I don't understand why that is the case, could you please provide an explanation?
Thanks in advance.
Support, please support.
Hi, since the question was asked by @bmulinari and you have added the last response, questions become invisible from our dashboard. This is the reason why we could not prioritize to answer this question. Sorry for the late response.
@bmulinari can you please send the project again, because when I try to download the application, it gives a 502 bad gateway error? I have reviewed it before but I could not find it in my workspace for now.
I will prioritize it and will fix your problem when you send your email. So, please let me know.
Regards.
@EngincanV, I have sent the e-mail again with the code.
Hi! I apologize for the broken link. I've shared a new by mail.
Let me know if you need anything.
Hi, @EngincanV. As requested, I've sent the application code and added a bit of context to the issue mentioned here.
Let me know if you need anything else, thanks!
Hi there. I see that 8.3.3 is out, but I couldn't find a mention of this in the release notes. Could you please confirm whether this issue was fixed in this release?
Thank you. Are there any workarounds we could use for fixing this issue until we wait for the next release?