ethSendRawTransaction return an "invalid sender" randomly!

[fred06130]

I generate a rawTransaction and on EthSendTransaction eth = web3.ethSendRawTransaction(hexaRawSignedTransaction).sendAsync().get(); i got an "invalid sender". I do not understand why, i have on myDapp decoded the raw sent and i retrieve the right sender.
Android web3j 4.8.8 lib used on testnet Sepolia via Alchemy.
Here the transaction raw: Sending Transaction(222): 0xf86c8202598444b580e38252089433e267cea3ab8505c35ff55de8c0faa85d712060872386f26fc10000801ba0dffc4a823d8ae8e9d101245534a0e7f8ca084fdf35a813e1b7edee32a55815fda0956c6d94d4631ab2180df966bae9976578e6fba9a02d94494ec9e3abe6df2e32

Log of decode raw:
2024-03-19 15:27:17.892 8262-8262 Web3jServiceManager com.st.st25nfc.dbg D ===> Transaction decode
2024-03-19 15:27:17.893 8262-8262 Web3jServiceManager com.st.st25nfc.dbg D Nonce :601
2024-03-19 15:27:17.893 8262-8262 Web3jServiceManager com.st.st25nfc.dbg D Gas Price :1152745699
2024-03-19 15:27:17.893 8262-8262 Web3jServiceManager com.st.st25nfc.dbg D Gas Limit :21000
2024-03-19 15:27:17.893 8262-8262 Web3jServiceManager com.st.st25nfc.dbg D Receiver @ : 0x33e267cea3ab8505c35ff55de8c0faa85d712060
2024-03-19 15:27:17.893 8262-8262 Web3jServiceManager com.st.st25nfc.dbg D Value : 10000000000000000
2024-03-19 15:27:17.893 8262-8262 Web3jServiceManager com.st.st25nfc.dbg D Data :
2024-03-19 15:27:17.947 8262-8262 Web3jServiceManager com.st.st25nfc.dbg D From : 0xb2e34b6b8916e5af05db99f3855540a5c22b2b6e
2024-03-19 15:27:17.968 8262-8262 Web3jServiceManager com.st.st25nfc.dbg D ChainID :null
2024-03-19 15:27:17.968 8262-8262 Web3jServiceManager com.st.st25nfc.dbg D Signed raw Transaction decode From :0xb2e34b6b8916e5af05db99f3855540a5c22b2b6e
2024-03-19 15:27:17.968 8262-8262 Web3jServiceManager com.st.st25nfc.dbg D Sent message : invalid sender
2024-03-19 15:27:17.968 8262-8262 Web3jServiceManager com.st.st25nfc.dbg D Sent json : 2.0

Does anyone have an idea or got this kind of random issue?
I saw in web3j upper version bug list, that there is somes patch for encoding and sepolia, not on the android releases. I use legacy transaction, does this could be a possible source of issue found?
Tks in advance

[ShubhamChouksey123]

I did the Transaction decode of your signed message :

utils.RLP.decode("0xf86c8202598444b580e38252089433e267cea3ab8505c35ff55de8c0faa85d712060872386f26fc10000801ba0dffc4a823d8ae8e9d101245534a0e7f8ca084fdf35a813e1b7edee32a55815fda0956c6d94d4631ab2180df966bae9976578e6fba9a02d94494ec9e3abe6df2e32")
[ "0x0259", "0x44b580e3", "0x5208", "0x33e267cea3ab8505c35ff55de8c0faa85d712060", "0x2386f26fc10000", "0x", "0x1b", "0xdffc4a823d8ae8e9d101245534a0e7f8ca084fdf35a813e1b7edee32a55815fd", "0x956c6d94d4631ab2180df966bae9976578e6fba9a02d94494ec9e3abe6df2e32" ]

Yes, the from/sender is wrong. You can use this https://playground.ethers.org/ playground to decode.