This issue has nothing to do with signing messages... what Lucius was talking about was copying an address from the "Sign message" dropdown list of addresses rather than clicking on the "Receive" tab...

When you use the "Sign Message" dropdown box... it shows several hundred addresses and I believe it actually includes "change" addresses as well. In addition, these addresses are not necessarily displayed in chaincode order... so the first address displayed is not necessarily address m/49'/0'/0'/0.

The issues this causes are that if you use one of the addresses from this dropdown list as a "receive" address... it's possible you're actually selecting some address way down the chain like address m/49'/0'/0'/87... which is likely to be out past the "gap limit" that the Ledger wallet is using when looking for addresses with transaction history etc. So, if you receive coins to it, Ledger wallet won't find the transaction.

Anyway, this situation doesn't seem to apply to the OP as they're saying they used the "receive" tab, which should use the first "unused" receive address. So, they either entered the Bitcoin address incorrectly (although I'm not even sure what the odds of generating a valid address when mistyping an address are? )... or they're done something weird like accidentally use a Litecoin address or something like that.

It would help if the OP still has the photo they took of the original address... without that it will be difficult to prove/disprove the mistyped address scenario. Although, using the "Signed Message" option, you can start typing an address and it shows the partial matches. ("Settings -> Tools -> Sign Message", click the "Address" box and type the first couple of characters of the address).