isonar --> Hi! How do I bypass the transaction confirmation screen when user tries to execute a non-transfer transaction?

Benji | NEAR --> Wdym by a non transfer transaction? If there’s no funds being transferred or anything that requires a full access key, there shouldn’t be a transaction confirmation

isonar --> Yes, it shouldn’t 🙂 but somehow when I call a contract method, I still get redirected to the confirmation screen…

Benji | NEAR --> That means u didn’t log into the correct contract so ur app doesn’t have an access key for your account to call methods on the contract

isonar --> aha! that’s may be what it is… let me check

isonar --> Yes, that was the reason. Thanks <@!Benji | NEAR>

AnkushSantra --> Good Evening, everyone. Everyone here is a blockchain expert. Can someone guide me on how to start my blockchain journey? Thank You!

Dorian | NEAR --> Hello!

Dorian | NEAR --> I’d suggest checking out https://www.near.university/ A program we developed to help give new users path to learn about becoming NEAR developer and you can get a high level overview of blockchain 🙂

omniscientsquid --> Hi, I am trying to get a simple near login to work with my react app running html/js. Webtech such as react are very new to me so please excuse my ignorance. I am trying to provoke a near-api-js requestSignIn to work, but getting an error ‘Uncaught (in promise) ReferenceError: Buffer is not defined’

I dont know if this is a node/react issue or something I have done wrong with the js. I have ensured Buffer is installed with npm, and found some suggestion online that placing this in the main js file will fix it;

import * as buffer from ‘buffer’;
(window as any).Buffer = buffer.Buffer;

However, ‘window’ isn’t accessible through the react framework (or at least it doesn’t seem to be). Does anyone have a suggestion as to where I am going wrong? The code is copied below.

omniscientsquid --> I think I have fixed it with adding ‘global.Buffer = global.Buffer || require(“buffer”).Buffer; // eslint-disable-line’ just under the imports. I have also noticed there is a stackoverflow link for questions, so will head over there next time.

nrmmyth --> Hey friends, is my understanding correct that https://rpc.testnet.near.org is a centralized API run by Near foundation?

ottpeter --> hi
There is this known problem when updating a contract at the same account/address.
https://stackoverflow.com/questions/60767120/getting-cannot-deserialize-the-contract-state-when-calling-rust-init-function
In this example https://examples.near.org/FT a sub account was created, which would solve this problem I guess. Is there a way to switch to a sub account in the browser when testing an app?