Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android messages won't open (error: 400) #1575

Open
marcolopes opened this issue Aug 18, 2019 · 15 comments

Comments

@marcolopes
Copy link

commented Aug 18, 2019

ANDROID MESSAGES won't open. Shows browser error:

400. That’s an error.
The requested URL was not found on this server. That’s all we know.

@maryadavies

This comment has been minimized.

Copy link

commented Aug 19, 2019

I've been getting the same error. Reloading it seems to fix it, but I think someone needs to check this.

I'm on 5.2.1 beta 1.

@cdnnhicks

This comment has been minimized.

Copy link

commented Aug 19, 2019

I've had the same issue for a few days. Sometimes a reload will work. Other times, I have to remove and add the service completely. I'm running Win 10 1903 and Franz version 5.2.0

@marcolopes

This comment has been minimized.

Copy link
Author

commented Aug 19, 2019

RELOAD won't fix in my case... Franz restart won't fix either.

@k1sr

This comment has been minimized.

Copy link

commented Aug 20, 2019

Not working here either, although the website and PC app work fine, which seems odd, given Franz is really just a wrapper for the web app... Unless they've added something to check if you're using a 3rd party app to access the url??

@misteroh

This comment has been minimized.

Copy link

commented Aug 21, 2019

Crappy temporary bandaid "fix" here:

  1. While in the Android Messages service, open View > Toggle Service Developer Tools (Ctrl/Cmd + Shift + Alt + I)
  2. In that new section that showed up, do you see that topbar with Elements / Console / Sources / Network / Performance / Memory / Application / etc...? Click on Application
  3. On the left hand side, click on Service Workers
  4. Click on the checkmark that says Bypass for network

Now as long as you have this Developer Tools window open, Android Messages will work even if you refresh.

Not ideal obviously but it will make do until this is fixed.


Poking around in the dev tools, I think the issue is centered around a service worker.

On initial load, https://messages.google.com/web/ loads fine and it spins up a service worker I assume for offline mode and other features. In any subsequent reload, the service worker intercepts the GET to https://messages.google.com/web/ and returns a 400 which displays the error message we're all seeing now. Why? I'm not really sure.

@adlk or @dweinberdweinber thoughts?

@maryadavies

This comment has been minimized.

Copy link

commented Aug 21, 2019

Thank you. Hopefuly there can be a more perm fix.

@Paladin173

This comment has been minimized.

Copy link

commented Aug 21, 2019

getting same issue on my end.

@pllgr

This comment has been minimized.

Copy link

commented Aug 23, 2019

same issue. My temp fix is deleting the service, re adding it.
Works for a few days then stops working

@Paladin173

This comment has been minimized.

Copy link

commented Aug 23, 2019

Crappy temporary bandaid "fix" here:

1. While in the Android Messages service, open `View` > `Toggle Service Developer Tools (Ctrl/Cmd + Shift + Alt + I)`

2. In that new section that showed up, do you see that topbar with `Elements` / `Console` / `Sources` / `Network` / `Performance` / `Memory` / `Application` / etc...? Click on `Application`

3. On the left hand side, click on `Service Workers`

4. Click on the checkmark that says `Bypass for network`

Now as long as you have this Developer Tools window open, Android Messages will work even if you refresh.

Not ideal obviously but it will make do until this is fixed.

Poking around in the dev tools, I think the issue is centered around a service worker.

On initial load, https://messages.google.com/web/ loads fine and it spins up a service worker I assume for offline mode and other features. In any subsequent reload, the service worker intercepts the GET to https://messages.google.com/web/ and returns a 400 which displays the error message we're all seeing now. Why? I'm not really sure.

@adlk or @dweinberdweinber thoughts?

Easy fix it seems, why hasnt it been implemented yet?

@marcolopes

This comment has been minimized.

Copy link
Author

commented Sep 12, 2019

Crappy temporary bandaid "fix" here:

  1. While in the Android Messages service, open View > Toggle Service Developer Tools (Ctrl/Cmd + Shift + Alt + I)
  2. In that new section that showed up, do you see that topbar with Elements / Console / Sources / Network / Performance / Memory / Application / etc...? Click on Application
  3. On the left hand side, click on Service Workers
  4. Click on the checkmark that says Bypass for network

Now as long as you have this Developer Tools window open, Android Messages will work even if you refresh.

Not ideal obviously but it will make do until this is fixed.

Poking around in the dev tools, I think the issue is centered around a service worker.

On initial load, https://messages.google.com/web/ loads fine and it spins up a service worker I assume for offline mode and other features. In any subsequent reload, the service worker intercepts the GET to https://messages.google.com/web/ and returns a 400 which displays the error message we're all seeing now. Why? I'm not really sure.

@adlk or @dweinberdweinber thoughts?

Does NOT work for me. After you restart Franz (needed, because it misbehaves a lot, service screens do not work from time to time, even using RELOAD - app get's all messes up)

Only way is to remove and ADD the service again, and NOT restart Franz , otherwise, error again!

@Paladin173

This comment has been minimized.

Copy link

commented Sep 12, 2019

I use this service a lot, and I wish we could get more focus on it to get it fixed.

@marcolopes

This comment has been minimized.

Copy link
Author

commented Sep 12, 2019

I use this service a lot, and I wish we could get more focus on it to get it fixed.

Me too. It's on my TOP list (first one really!).

If i didn't have to RESTART Franz... but it "freezes" a lot, specially after windows SUSPENDS and wakes up for next work session... :\

@misteroh

This comment has been minimized.

Copy link

commented Sep 12, 2019

@marcolopes

As stated in the original post:

Now as long as you have this Developer Tools window open, Android Messages will work even if you refresh.

View > Toggle Service Developer Tools (Ctrl/Cmd + Shift + Alt + I)

You don't need to remove and add the service as long as the Developer Tools window is open.

@themagpieswarble

This comment has been minimized.

Copy link

commented Sep 18, 2019

@marcolopes
You don't need to remove and add the service as long as the Developer Tools window is open.

Not working for me either.

I load in Android Messages as a new service just to start fresh, while it's still working I follow your directions, I right click Android Messages and click 'Reload' to test it, and it loads with the 400 error. Doesn't matter if Dev Tools window is still open on the side with the 'Bypass for network' box checked and/or the 'Update on reload' box is checked (like someone suggested in another thread.)

I've also tried doing this after Android Messages 400 error appears and it doesn't seem to matter.

How annoying. Seems like this would be an easy fix and it's been going on for over a month now.

@ryan-rokusek

This comment has been minimized.

Copy link

commented Sep 18, 2019

The workaround isn't working for me either.

OSX: 10.14.6
Franz: 5.3.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
9 participants
You can’t perform that action at this time.