Fix: log the resolved OFT wrapper address (not the optional param) to avoid undefined in errors #1677
+16
−11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue:
Show misleading error message:

Root cause:
error logs referenced the optional input
oftAddress. When callers didn’t pass it, the log showed OFT: undefined even though we had already resolved the actual wrapper via getOAppAddressByEid(...).Change:
oftWrapperAddress.wrapperAddresstooftWrapperAddressfor clearification.