bip39 tool created a private key that cannot be imported

Question

I have a mnemonic phrase generated by the bip39 tool.

(The prior use case was that program uses the public keys in an array and people send to the one they randomly get. Occassionally when an address gets funds an admin goes and retrieves the private key to move the funds)

In any case, one of the addresses in the high hundreds does not import. Its private key gets an error that it is malformed.

Expected private key to be an Uint8Array with length 32

What can I do about that? This is the first time I've encountered that and the other private keys from this mnemonic phrase and derivation path work.

It seems like I could simply import the mnemonic phrase itself and add that many accounts, but this will be very time consuming. So, it also seems like a glitch, so reporting it here.

edit: I imported the mnemonic phrase into metamask, and recorded a screen macro of importing accounts, which I let run for several hundred times until the address I wanted was added. There is no batch feature in metamask as metamask's features are based on what most people do. Metamask was able to resolve that address and sign and broadcast transactions, which you would think must use the same private key. I guess there is no actual error with the private key, only library validation of it, which should be further investigated.

Answer 1

Try to generate the addresses this way. Pass your Bip39 seed to it. Generate as much addresses. let me know if the issue persist

import ethers from 'ethers'
    const ethHDW = async (seed) =>{
        return new Promise(resolve => {
    
            const ethNode = ethers.utils.HDNode.fromSeed(seed)
            const derived =  ethNode.derivePath("m/44'/60'/0'/0/0")
    
            resolve(derived)
        })
    }

For each address you increase the last 0.