mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #3098] [bug]: When installed as Chrome PWA the first tab url is always overridden with the default 'https://echo.hoppscotch.io' request #1018
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1018
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @stefankorun on GitHub (May 31, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3098
Is there an existing issue for this?
Current behavior
Bug behaviour
While using the installed PWA in Chrome (Version 114.0.5735.45 (Official Build) beta (arm64)) when I start or refresh the application, my first tab request is always replaced with
https://echo.hoppscotch.io:https://github.com/hoppscotch/hoppscotch/assets/2415410/b38201dc-7668-4fc8-b27c-6a40ff1b2d9f
Expected behaviour
When using the app via browser, the tab url correctly persists between tab reloads and closing:
https://github.com/hoppscotch/hoppscotch/assets/2415410/e97dad2d-83c5-4c43-bf9d-68ce95daefa8
Steps to reproduce
https://echo.hoppscotch.ioto any other (e.g.https://ifconfig.me/)https://echo.hoppscotch.ioinstead ofhttps://ifconfig.me/Environment
Production
Version
Cloud
@liyasthomas commented on GitHub (May 31, 2023):
Hi @stefankorun, sorry for the inconvenience caused. We were able to reproduce the bug and are working on patching it as soon as possible.
@stefankorun commented on GitHub (May 31, 2023):
@liyasthomas Awesome, thank you for the quick response. Open to contributing if needed.
@liyasthomas commented on GitHub (Jun 12, 2023):
We've patched this issue in the latest release.