Skip to content

Update near mobile#78

Open
AgustinMJ wants to merge 5 commits intoazbang:mainfrom
Peersyst:feat/update-near-mobile
Open

Update near mobile#78
AgustinMJ wants to merge 5 commits intoazbang:mainfrom
Peersyst:feat/update-near-mobile

Conversation

@AgustinMJ
Copy link

@AgustinMJ AgustinMJ commented Mar 11, 2026

Fixes sign in with near mobile and improves implementation.

Closes #63

Copy link
Contributor

@frol frol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a couple of quick comments/questions


"permissions": {
"storage": true,
"location": true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is location access is needed? I am mostly just curious, not a blocker for me

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We use window.selector.location to show it in the UI.

"permissions": {
"storage": true,
"location": true,
"allowsOpen": ["https://nearmobile.app", "https://play.google.com", "https://apps.apple.com"]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In my testing the old version on the mobile devices, I realized that this list needs to be extended with "https://near-mobile-signer-backend.peersyst.tech" as it was used to open the mobile app when clicking on "Sign transaction". Have you tested your new plugin to work on the mobile devices?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right! In the new version we use https://near-mobile-production.aws.peersyst.tech. Updated!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since you only removed NEAR Mobile, I wonder whether these changes are needed. Can you comment on pros/cons of these?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It solves this issue #63. I forgot to link it, my bad!

"@types/node": "^24.9.1",
"@walletconnect/modal": "^2.7.0",
"borsh": "^2.0.0",
"near-api-js": "^4.0.0",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It wasn't here before, and it seemed to work fine. Was it just a coincidence that near-api-js was just inherited from @peersyst/near-mobile-signer?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was being installed by @peersyst/near-mobile-signer but was also being used by other wallets.

@frol
Copy link
Contributor

frol commented Mar 12, 2026

@AgustinMJ There are multiple bugs that I noticed over the current implementation:

  1. "Connect (With Signed Message)" does not work anymore (I have just fixed it recently, and apparently you did not incorporate those changes): https://github.com/azbang/near-connect/pull/77/changes#diff-26c9aedc14bb8dda7e8fd42cf7da91afb7718fd010250c0550857f6928836766
  2. "Connect (With Add Key)" works like "Connect (With Signed Message)" instead of actually adding the provided public key to the account
  3. "Approve in app" still does not work on iOS
  4. "Google Play" button has a broken layout on my iPhone 13 Pro
IMG_4463

Please, make sure you at least test all the buttons on the Example app (yarn run example)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

moduleResolution in near-wallets should be Bundler with Vite

2 participants