Copied blueprint macro raising error saying graph is linked private object

Hello I’m hear to share or asking some solution of copied macro is raising linkage error on save.
I have a blueprint class ‘A’ which is inherited from class ‘A0’ and Blueprint Macro library ‘B’ with A0.
I’ve made an bp macro from A and I wanna share this to all other classes from A0 so I copied it into ‘B’.
There’s no problem with editing bp and it compiles well with any problem.
But there’s an error occurred when I save the edited class A blueprint file saying the replaced macro function is linked to private external package.

Actually I have already know how to solve this problem. Because this is not the first time I have met the problem like this. So this is just an annoying situation which is hard to accept for me.

Because the solution is so simple and tiddy that If you create an empty Macro function on the B (which is same file to the moved function) and setup the whole input and output pins and copy the entire macro function contents into the new one, then you can see calling the new created function from A is no problem.

Are there any one who is suffered by this problem like me?
Or Is there any solution?