OTAA failed / Debugging device activation OTAA issues

No, you didn’t.

You made a request to replace Semtech’s packet forwarder with an oddly maintained fork, and your request was supported with zero explanation of what specific behavior you were trying to change.

A bug report states specifically what is wrong. “Try this other thing instead” is neither a valid bug report, nor a valid change request.

If you can point to a specific behavior difference between Kersing’s forwarder and Semtech’s, then you might see some willingness to change things - eg. quote a transmit request which is honored by one and dropped or misexecuted by the other.

Even better, point out the specific lines of code which cause this difference, and submit a pull request to Semtech’s repo which implements that fix. Then ask RAK to include that in their lightly customized version.