You should've said it along with other info earlier in the OP

I've tried the manual update (help->Check for updates) and mine also failed to connect to the update server.
Unlike you, I'm not using a VPN and I have also tried disabling the firewall and other versions, namely: 3.3.7 and 3.3.8.
Electrum on the other hand works fine.

I opened a new issue: https://github.com/spesmilo/electrum/issues/5899 (Update Check Failed #5899)
Hopefully, they'll fix it up asap.

Try listenonion=0 the default is '1' enabled.

Also, change your invalid config "rpctimeout" to "rpcservertimeout" in order to remove the very first error in your debug log.

Must be a connection issue.

If you do not want to receive any update notification, you can disable it in the settings.
Click "Tools"->"Preferences"->Click "General" Tab-> and disable "Automatically check for software updates".

Those outputs are P2PK and the result shows the pubkey not the pubkeyhash. There's no derived address which it should be.

Chainquery somehow displays an address for those type of outputs, maybe because it uses BitcoinCore Version 0.18.0.
0.19.0.1 have this in the changelog:
But it's for decoderawtransaction.
Is it because getrawtransaction verbose "true", decodes the raw transaction result like decoderawtransaction?

Off-topic: Those transactions looks like used for something else though.
I can't read anything from the OP_Return of the transactions that spent the outputs.

Don't forget the fact that it's a physical store with CCTV not available online, so no one in the right mind would double-spend a 5$ transaction just for a test.
Just try it an you'll find your face in a mugshot  

Their problem is the fee and purchase amount, did they have a minimum?
For the minimum allowed amount, if they are taking too much 1$ transactions, they will lose more bitcoins as a transaction fee for consolidating those satoshi.
It's better if they only accept Bitcoin for $5 and above transactions.
For the fee, there was a time that a 1sat/byte can take days to confirm or even drop after 2weeks,
that's a Dec 2017 thing, but still applicable today though.

Not that "blockchain", based from "wallet ID" you're talking about the online wallet of blockchain.com/info.
And it isn't Bitcoin's blockchain, they have a "blockexplorer" service but it's not affiliated with Bitcoin, they just used the name.

If it's the earliest versions of Bitcoin-cli, there's no other way but to recover that wallet.dat or any latest backup of it.

That was back then, when there's no Electrum versions for Bitcoin Cash and of course, those Bitcoin forks.
Now, it's as easy as: export private key(s) from Armory (procedure) then import them to each Electrum forks depending on the coin.
You might want to send your Bitcoins to another address before exporting them.

Electrum forks:
Bitcoin Cash [BCH] - https://electroncash.org/
Bitcoin SV [BSV] - https://electrumsv.io/
Bitcoin Gold [BTG] - https://github.com/BTCGPU/electrum

Though, you will encounter some issues for P2SH-SegWit addresses, but for legacy, it's very simple actually.

FYI, it's in Bitcoin Cash's blockchain, not in any wallet.
To check if it went through, paste the address here: https://www.blockchain.com/explorer?view=bch_blocks When prompted to select a chain, select BCH.
Note: It will be displayed as BCH address (starts with 'q') instead.
Cashapp didn't received it because their system is designed for Bitcoin and isn't connected to a Bitcoin Cash blockchain.

Like previously said, you need to get the private key of that address to be able to restore the address to a wallet that's connected to Bitcoin Cash blockchain.

Customer service must be for non-technical queries or they are clueless of those issues because they just added this "virtual currency" feature lately.
I can't believe they don't include a warning about sending forked coins to the address and doesn't have a forked coin recovery policy.

But I've found this from their TOS2:
Looks like they wont help you recover your coins after all.

---

You mentioned "word phrases", is it from cashapp? AFAIK, cashapp doesn't have a seed phrase.

Cash app have your addresses' private keys which is the only way to recover your Bitcoin Cash.
It's simple if you just sent it to a "real" bitcoin wallet like Electrum/BitcoinCore; unfortunately, 'Cash App' is a custodial service.

Do as what Bitcoin(.)com told you because they are the only one who can help you with this.
Tell them that it's Bitcoin Cash [BCH] that you've sent to your (wife's) Bitcoin [BTC] address.

AdolfinWolf's post should work, have you included the apostrophe (') after the '0'? It should be added.

Also, you shouldn't be looking in the receive tab, open the addresses tab by clicking "view->show addresses"
Then click 'addresses' beside 'Coin Splitting' tab.

After confirming that the address is there, just open ElectrumSV's wallet file using Electrum (browse to the location).

There are wallets that used mnemonic seed even before BIP39 was introduced. But it's certainly not Bitcoin Core.
Electrum for example had their own seed words implementation and 1.8.1 was released on Aug 2013(?). IDK the exact date and the older version's dates.

It will be rejected by nodes including the one where your client is connected; non-broadcast transaction won't exist in the blockchain.

---

The description of your scenario including your previous replies require CLTV scripts to work, but instead of sending to an address behind your no-passphrase seed,
the funds needs to be directly sent to a P2SH address which has a "rule": [Read BIP65]

You can spend the funds sent to that address whenever you want (timer starts after the transaction), but when the expiry time passed, your heir can spend it instead.
It's also possible to use the funds without creating another script by using it as the change address (but that involves address reuse!).

The problem is there's no known non-custodial client that utilizes those scripts

Seed phrase isn't available at that time or even today as BIP39 wasn't implemented to BitcoinCore.
It wasn't even HD at that time either, it's all random private keys so your older backups might contain outdated number of keys than the one you've used beforeafter you saved that backup.

The old wallet files might work because AFAIK devs have been keeping backwards compatibility but if you stumbled upon a problem,
there are available tools like "pywallet" to read/extract the keys from your wallet.

It's the same for fiat and crypto, it's just not totally necessary to send it back to your bank if you're going to trade later.
The difference is if it's crypto, you have a better choice than holding it in an Exchange
because you will have the full control of your funds if you have the private keys of your addresses (in a desktop wallet).

Don't worry, Coinbase so far is doing a good job on keeping hackers at bay,
the most probable issue that you might face in the future is the one I've mentioned in my previous reply.

No, sry I didn't noticed the "USD".
So if it's in fiat, the only choice you have is to keep it in Coinbase. Sending back to your Bank isn't necessary unless if it will take a while before you decide to trade again.

You just 'saved' it and wasn't broadcast yet to the network.

You can safely delete it from the history by doing right-click->delete (do not right click to the label, point to the date) and your previous balance should return.
You can also broadcast it (double-click and click "broadcast") if you want the transaction to proceed.

The simplest setup is to create a signed transaction with locktime of about <12months from now and give the "signed Raw transaction" to your beneficiary.

He won't be able to broadcast it during that 12 months.
Before the locktime date come and you're still 'kicking', you can create another normal transaction spending the inputs used by the "timelock" transaction. That will make it invalid.
Create another locktime transaction using the new input and contact 'him' about replacing the signed RAW transaction that you've gave previously.

Repeat the process for every "extension".

If you're using Trezor, read this: https://wiki.trezor.io/User_manual:Using_locktime

You're trading using the Coinbase not 'Coinbase Pro'?
That's very inefficient, even with the huge difference of price when you bought them; not to mention the withdrawal fee.

As for your query: It's relatively safe, they will handle the keys and thus the security of your funds for you in exchange for "trusting" them (newbie-friendly way to hodl).
The problem is the risk of locking your funds, they may issue a higher KYC requirement once you've reached a higher accumulated deposits.
If you're fine risking that amount, you can keep it there.
If not, send it to your Electrum on a very safe PC or a hardware wallet like Trezor/Ledger.

P.S: This is getting off-topic with the OP, you should consider creating a new thread about the this topic and lock this one using the "lock" button below (lower-left).

When you click "reload account", mycelium will re-sync and search for your selected account's transactions from scratch,
is the "syncing in progress...." in the accounts tab still displayed? If yes, wait for it to finish.

Also, do address '123' and address '1234' starts with a different character, say '3', 'bc1' or '1'?
Because, you might have clicked the QR code in the balance tab that changed the displayed address (no worries: all are included to your account),
but still it will be automatically replaced once you've received a transaction.

Lastly, paste your receiving address "123" to a blockexplorer (https://www.blockchain.com/explorer) to confirm if there's really a transaction before trying to recover anything.

Take note: In your 1st transaction, 'Trusted Coin' (Electrum's 2FA provider) will deduct some bitcoins from your balance as a payment.
If you're not willing to pay for their service, I suggest you to disable 2FA first before sending any transaction. But 2FA will give you a better security.
For example: if your system was compromised, the hacker wont be able to send out your coins even if he have access your password and wallet file.

To create a version of your current wallet with disabled 2FA, click "new/restore", select "wallet with two factor authentication"-> "I already have the seed" (paste your wallet's 12-word seed), click 'next' and tick "disable".
Finish the creation process then use it to send your bitcoins instead of the 2FA enabled one.

But if you're willing to pay 0.001 BTC as a payment for the next 20 transactions (including the 1st), keep on using it.
That "one time password" should be in your Phone's authenticator app that you used to setup Electrum [2FA] wallet, it'll give you different code in every attempt.