[Google Pixel 6] badabing2003:
I hate coding a temporary fix only to ditch it later,

Adding UI to WxPython takes effort, it's not the simplest (yeah there is no WYSIWYG)

If Google comes up with a new Platform tools that is required to flash the next month's release, I'd have to rush a release to undo my changes, otherwise people would be blocked.

I much rather have the newbie come and ask questions here, and in the process learn a thing or two.

It was never the intent of PF to make it dummy proof, it is and it remains a tool that automates the steps and does validations to avoid manual mistakes, and I put out as much logging as possible to provide valuable details on what is going on, at each step of the way (there is even undocumented graphical/visual log, that one day I need to document)

I encourage people to learn.

PF doesn't have any issues with package name, and flashing is agnostic to Magisk's package name.

I bet you, the unhide did not properly do its job, hence why you ran into issues.

Here's how PF works.

If you're rooted (requires adb su rights to detect), it fetches Magisk Core version (/data/adb/Magisk)

If you have Magisk app installed, and have the proper package name, hence it finds it, it fetches Magisk application version.

At patch time it takes a decision about which to use to create a patch

If versions are the same, or core is > app then it uses the core, and for this it doesn't matter the package name, it uses patch_boot to create the patch, and this is typically the most used option.

If you happen to have upgraded Magisk application, but not the core, then it assumes that you want a newer core as well, in which case it unpacks the application and uses it to create a patch.

If the application is hidden, stub is not enough to create a patch, and PF will tell you about it.

(Recommendation: If you're rooted, grant root access to adb, and never have to worry about un-hiding the app to create a patch)

If you have the application installed, but the package name is not set, PF thinks that you don't have the application installed,

If you're rooted, no issues, it will use the root Magisk and not care about that.

But if you're not rooted and you don't have an app installed (or PF couldn't find it because the package name is not matched) then PF will show the Magisk Install dialog but before that it will give you plenty of warning, and depending on which Magisk you install, it will set the package name correctly.

So let's say that you even went as far as installing Magisk even though you had Magisk installed which PF did not find because of mismatched package name, if your installed Magisk is from the same source (ie same package name) then it would just be replaced and package name set, unpacked and used to create the patch.

The only reason package name is needed is to find the application apk and unpack it, it has no relevance in the patch output,

What is relevant is if you have more than on Magisk on your system, one hidden and the other not (and yes, sometimes unhiding does not properly remove the hidden stub), or from two different source with different package name (this I'm not even sure about).

If you want to know exactly what happened in your case, provide support file and I'll take a look.