adding "sending address" in bitcoin core fails

[citb0in]

Hello, I have created a wallet in bdb format with avoid_reuse=false in Bitcoin Core 26.0.0 for testing purposes and imported the corresponding transactions manually using importprunedfunds. This worked for all incoming payments, i.e. incoming transactions. Unfortunately I could not import the outgoing transactions with this command, the error message appears:

No addresses in wallet correspond to included transaction (code -5)

So I checked the windows "Receiving Addresses" and "Sending Addresses". Under "Receiving Addresses" I see my wallet address as expected, that's why the importfunds worked for incoming transaction. I'm pretty sure Bitcoin core expects to see my wallet address under "Sending Addresses" but this window is empty. So I create to add my same address to "Sending Addresses", too. But it fails with the error message:

Address "123foobar" already exists as a receiving address with label "foo" and so cannot be added as a sending address

I am aware about the risk of reusing a address, but as this is only for testing purposes with no valuable coins in there I know what I'm doing. I just like to import the outgoing transactions, too. What am I missing here? Do I need to start bitcoin core with any certain parameter that to override maybe a deprecated option that I'm not aware of ? Or is this a still unsolved bug ? Any help appreciated. Thanks

[nc50lc]

I'm pretty sure Bitcoin core expects to see my wallet address under "Sending Addresses" but this window is empty. So I create to add my same address to "Sending Addresses", too.
-snip-
Or is this a still unsolved bug ? Any help appreciated. Thanks

Since the issue is currently "Open", it's not yet solved in the latest build.

If you really want to import those transactions (with that bug), since it's non-descriptor, you can import any of the outbound txn's outputs' address as watching-only.
The outgoing txn's output will be included to your "Watching-only" funds, spending the previous inbound transaction's output.

But the best workaround if the goal is to spend a pruned output is to import only the pruned transactions that aren't spent yet, just do not import the spent ones.
This doesn't solve the linked issue's OP though.