A cookie associated with a cross-site resource at <a href='http://unpkg.com/'>http://unpkg.com/</a> was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application&gt;Storage&gt;Cookies and see more details at <a href='<a href='https://www.chromestatus.com/feature/5088147346030592'>https://www.chromestatus.com/feature/5088147346030592</a>'>https://www.chromestatus.com/feature/5088147346030592</a> and <a href='<a href='https://www.chromestatus.com/feature/5633521622188032'>https://www.chromestatus.com/feature/5633521622188032</a>'>https://www.chromestatus.com/feature/5633521622188032</a>. DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/contentscript.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/inpage.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME (index):1 A cookie associated with a cross-site resource at <a href='http://www.moneybutton.com/'>http://www.moneybutton.com/</a> was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application&gt;Storage&gt;Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032. (index):5760 id #nav-search DevTools failed to load SourceMap: Could not load content for <a href='https://unpkg.com/@popperjs/popper.min.js.map:'>https://unpkg.com/@popperjs/popper.min.js.map:</a> HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load SourceMap: Could not load content for <a href='https://unpkg.com/tippy-bundle.umd.min.js.map:'>https://unpkg.com/tippy-bundle.umd.min.js.map:</a> HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE (index):5833 Settings = {wallet: {…}} sign.js:245 sessionToken = null inpage.js:1 MetaMask: MetaMask will soon stop reloading pages on network change. For more information, see: <a href='<a href='https://docs.metamask.io/guide/ethereum-provider.html#ethereum-autorefreshonnetworkchange'>https://docs.metamask.io/guide/ethereum-provider.html#ethereum-autorefreshonnetworkchange</a>'>https://docs.metamask.io/guide/ethereum-provider.html#ethereum-autorefreshonnetworkchange</a> Set &#39;ethereum.autoRefreshOnNetworkChange&#39; to &#39;false&#39; to silence this warning. (anonymous) @ inpage.js:1 setTimeout (async) t.exports @ inpage.js:1 initProvider @ inpage.js:1 (anonymous) @ inpage.js:1 1../lib/auto-reload.js @ inpage.js:1 i @ inpage.js:1 e @ inpage.js:1 (anonymous) @ inpage.js:1 (anonymous) @ contentscript.js:1 1.@babel/runtime/helpers/interopRequireDefault @ contentscript.js:1 i @ contentscript.js:1 e @ contentscript.js:1 (anonymous) @ contentscript.js:1 (index):5880 text = test sign.js:143 signing undefined sign.js:154 got hash DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/contentscript.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/inpage.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME inpage.js:1 MetaMask: MetaMask will soon stop reloading pages on network change. For more information, see: https://docs.metamask.io/guide/ethereum-provider.html#ethereum-autorefreshonnetworkchange Set &#39;ethereum.autoRefreshOnNetworkChange&#39; to &#39;false&#39; to silence this warning. (anonymous) @ VM151 inpage.js:1 setTimeout (async) t.exports @ VM151 inpage.js:1 initProvider @ VM151 inpage.js:1 (anonymous) @ VM151 inpage.js:1 1../lib/auto-reload.js @ VM151 inpage.js:1 i @ VM151 inpage.js:1 e @ VM151 inpage.js:1 (anonymous) @ VM151 inpage.js:1 (anonymous) @ VM150 contentscript.js:1 1.@babel/runtime/helpers/interopRequireDefault @ VM150 contentscript.js:1 i @ VM150 contentscript.js:1 e @ VM150 contentscript.js:1 (anonymous) @ VM150 contentscript.js:1 sign.js:189 error {reason: "invalid-app-domain", data: {…}} 2 Issues are as follows Indicate whether to send a cookie in a cross-site request by specifying its SameSite attribute Because a cookie&#39;s SameSite attribute was not set or is invalid, it defaults to SameSite=Lax, which will prevent the cookie from being sent in a cross-site request in a future version of the browser. This behavior protects user data from accidentally leaking to third parties and cross-site request forgery. Resolve this issue by updating the attributes of the cookie: Specify SameSite=None and Secure if the cookie should be sent in cross-site requests. This enables third-party use. Specify SameSite=Strict or SameSite=Lax if the cookie should not be sent in cross-site requests AFFECTED RESOURCES 3 cookies Name Domain & Path _ga .unpkg.com/ _gid .unpkg.com/ AWSALB www.moneybutton.com/ 25 requests core@2 core@2.4.4 popper.min.js tippy.js@6 tippy.js@6.2.5 tippy-bundle.umd.min.js autosize autosize@4.0.2 autosize.js moneybutton.js bitpacket bitpacket@0.0.18 bitpacket.min.js imb-permission-grant user_identity 7492 currency currency client_identifier=f7b46437bc9d72b82eabd9e435081793 white-isologo.svg permissions.png pay_blue.svg sign-in_yellow.svg lock_black.svg unlock_salmon.svg Learn more: SameSite cookies explained Indicate whether a cookie is intended to be set in cross-site context by specifying its SameSite attribute Because a cookie&#39;s SameSite attribute was not set or is invalid, it defaults to SameSite=Lax, which will prevents the cookie from being set in a cross-site context in a future version of the browser. This behavior protects user data from accidentally leaking to third parties and cross-site request forgery. Resolve this issue by updating the attributes of the cookie: Specify SameSite=None and Secure if the cookie is intended to be set in cross-site contexts. Note that only cookies sent over HTTPS may use the Secure attribute. Specify SameSite=Strict or SameSite=Lax if the cookie should not be set by cross-site requests AFFECTED RESOURCES 1 cookie Name Domain & Path AWSALB www.moneybutton.com/ 7 requests moneybutton.js imb-permission-grant user_identity 7492 currency currency client_identifier=f7b46437bc9d72b82eabd9e435081793 Learn more: SameSite cookies explained