fast-auth-signer
                                
                                 fast-auth-signer copied to clipboard
                                
                                    fast-auth-signer copied to clipboard
                            
                            
                            
                        Cannot do Near.call to thirdparty contracts using FastAuth-created account
Describe the bug
FastAuth-created account cannot sign transactions to third-party contracts on near.org, so if users go with the cool feature of near.org, they become hostages unable to interact with DevHub or any other BOS app that uses a custom contract (not social.near) even if they fund the account as signing with full-access key does not work.
To Reproduce
- Sign into FastAuth-created account
- Go to DevHub: https://near.org/devgovgigs.near/widget/gigs-board.pages.Feed
- Try to like or post something
- You won't be able to submit the transaction
Expected behavior
I should be able to sign a transaction to third-party contracts (non-social.near), and get the transaction relayed or prompted to fund my account with some NEAR to cover the fees.
Screenshots
Here is the video recording: https://www.loom.com/share/22744a79b3b54e56a9eae1ba7264977b
Thanks for filing this issue @frol ! I ran into the same paint points when onboarding ecosystem contributors to DevHub recently, as they could not interact with the platform via FastAuth accounts. 😞
It would be ideal if we could prioritize this issue as it's a critical developer engagement piece for the NEAR ecosystem.
@trechriron should this issue be transferred to fast-auth-signer or mentioned in a newly created one in that repo?
cc @DavidM-D @diogoortega
I have added to the Fast Auth project board in Triage status. We regularly look through defects and determine priority, severity, and assignment.
Actually, I need to transfer it so it shows properly. I suggest we submit all fast-auth defects to the #fast-auth-signer repo in the future. Thanks!
As of 11/15/2023, I'm able to create a post from a FastAuth account:
txn: https://legacy.explorer.near.org/transactions/DhDSuYixjYtEXfEKTmLtV8Gq2qSVTfsBL5aywEXftsGE#5i9MsvG74eyVm5SooTbnrQWTSqLPtnJQkNy7Cit37FTu
result post: https://near.social/devhub.near/widget/app?page=post&id=2129
But it is quite volatile, took me about 5 attempts to successfully submit this transaction. Unlike post from a wallet account, which is always successful
@DavidM-D Is this issue fixed?
@hcho112 is this still an issue? Do you know why transaction submission is so unstable? Is it reproducible?
Just ran into that @trechriron @volovyks any updates on this one?