You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When attempting to view the approvals page on the wallet address 0xa435c0Da6F7414b691eF1a2C64A3Eb1AD02b0989, only the skeleton of the approvals page is displayed, even after approving an NFT contract on the testnet at 0x7D2839746EbF8ec5F02eFd51fcCD4E4eBbc3b09B with token ID 1.
To Reproduce
Steps to reproduce the behavior:
Visit the wallet address 0xa435c0Da6F7414b691eF1a2C64A3Eb1AD02b0989 on the testnet.
Navigate to the approvals page.
The approvals page should only display a skeleton or loading state, even after approving the NFT contract.
Expected behavior
After approving the NFT contract at 0x7D2839746EbF8ec5F02eFd51fcCD4E4eBbc3b09B with token ID 1, the approvals page should display the approved contract, token ID, and any other relevant information.
Screenshots
Desktop (please complete the following information):
OS: MacOS
Browser: Chrome
Logs from console
app.1871a41d.js:1 Uncaught (in promise)
TypeError: Cannot read properties of undefined (reading 'length')
at app.1871a41d.js:1:165840
| (anonymous) | @ | app.1871a41d.js:1
-- | -- | -- | --
| await in (anonymous) | |
| addressIsContract | @ | app.1871a41d.js:1
| (anonymous) | @ | vendor.1c0f80b2.js:311
| getContract | @ | app.1871a41d.js:1
| (anonymous) | @ | vendor.1c0f80b2.js:311
| shapeErc721AllowanceRow | @ | app.1871a41d.js:1
| (anonymous) | @ | vendor.1c0f80b2.js:311
| (anonymous) | @ | app.1871a41d.js:1
| fetchAllowancesForAccount | @ | app.1871a41d.js:1
| await in fetchAllowancesForAccount | |
| (anonymous) | @ | vendor.1c0f80b2.js:311
| immediate | @ | 783.7d900319.js:1
| s | @ | vendor.1c0f80b2.js:36
| c | @ | vendor.1c0f80b2.js:36
| y | @ | vendor.1c0f80b2.js:36
| ge | @ | vendor.1c0f80b2.js:36
| me | @ | vendor.1c0f80b2.js:36
| setup | @ | 783.7d900319.js:1
| s | @ | vendor.1c0f80b2.js:36
| mr | @ | vendor.1c0f80b2.js:36
| pr | @ | vendor.1c0f80b2.js:36
| L | @ | vendor.1c0f80b2.js:36
| B | @ | vendor.1c0f80b2.js:36
| g | @ | vendor.1c0f80b2.js:36
| l | @ | vendor.1c0f80b2.js:36
| run | @ | vendor.1c0f80b2.js:36
| e.update | @ | vendor.1c0f80b2.js:36
| s | @ | vendor.1c0f80b2.js:36
| O | @ | vendor.1c0f80b2.js:36
| Promise.then | |
| A | @ | vendor.1c0f80b2.js:36
| E | @ | vendor.1c0f80b2.js:36
| ce | @ | vendor.1c0f80b2.js:36
| w | @ | vendor.1c0f80b2.js:36
| R | @ | vendor.1c0f80b2.js:36
| N | @ | vendor.1c0f80b2.js:36
| qe | @ | vendor.1c0f80b2.js:36
| (anonymous) | @ | vendor.1c0f80b2.js:36
| R | @ | vendor.1c0f80b2.js:36
| N | @ | vendor.1c0f80b2.js:36
| qe | @ | vendor.1c0f80b2.js:36
| (anonymous) | @ | vendor.1c0f80b2.js:36
| R | @ | vendor.1c0f80b2.js:36
| N | @ | vendor.1c0f80b2.js:36
| qe | @ | vendor.1c0f80b2.js:36
| set value | @ | vendor.1c0f80b2.js:36
| $ | @ | vendor.1c0f80b2.js:317
| (anonymous) | @ | vendor.1c0f80b2.js:317
| Promise.then | |
| F | @ | vendor.1c0f80b2.js:317
| U | @ | vendor.1c0f80b2.js:317
| goTo | @ | 246.f887aa8c.js:1
| onClick.n..n. | @ | 246.f887aa8c.js:1
| s | @ | vendor.1c0f80b2.js:36
| c | @ | vendor.1c0f80b2.js:36
| n | @ | vendor.1c0f80b2.js:36
!this.__accounts[n].addresses.includes(a) && (this.__accounts[n].processing[a] ? this.__accounts[n].processing[a] : (this.__accounts[n].processing[a] = new Promise((async e=>{
const t = (0,
_.zi)().loggedChain.settings.getIndexer()
, r = (await t.get(`/v1/contract/${a}`)).data.results.length > 0;
r || this.__accounts[n].addresses.includes(a) || this.__accounts[n].addresses.push(a),
e(r)
}
)),
this.__accounts[n].processing[a].then((e=>(delete this.__accounts[n].processing[a],
e))))))
The text was updated successfully, but these errors were encountered:
Bug Report
Describe the bug
When attempting to view the approvals page on the wallet address
0xa435c0Da6F7414b691eF1a2C64A3Eb1AD02b0989
, only the skeleton of the approvals page is displayed, even after approving an NFT contract on the testnet at0x7D2839746EbF8ec5F02eFd51fcCD4E4eBbc3b09B
with token ID 1.To Reproduce
Steps to reproduce the behavior:
0xa435c0Da6F7414b691eF1a2C64A3Eb1AD02b0989
on the testnet.Expected behavior
After approving the NFT contract at
0x7D2839746EbF8ec5F02eFd51fcCD4E4eBbc3b09B
with token ID 1, the approvals page should display the approved contract, token ID, and any other relevant information.Screenshots
Desktop (please complete the following information):
Logs from console
app.1871a41d.js:1 Uncaught (in promise)
The text was updated successfully, but these errors were encountered: