Ferdi: Regression with WhatsApp

[kytwb]

See https://github.com/kytwb/ferdi/pull/17#issuecomment-528880912:

It looks like v5.3.0 has some difficulties with the WhatsApp recipe. The recipe solves the "WhatsApp works with Google Chrome 49+" by removing the "Franz" from the user agent (meetfranz/recipe-whatsapp:index.js@9797764#L3), but this PR replaced Franz with Ferdi

[AGCaesar]

I changed all "Fanz" occurrences in ~.config/Ferdi/recipes/whatsapp/index.js to "Ferdi" and now it works great :)
Thanks for the 5.3 release!

[ZeroCool940711]

As an extra for those of us using Ferdi on Windows that folder mentioned before by AGCaesar can be located quickly by pressing Win+R and then typing %APPDATA%/Ferdi/recipes/whatsapp, that will take you directly to that folder.

[vantezzen]

This bug should be fixed quite easily by settings the user agent back to Franz's agent. This is best for keeping compatibility.
I am currently taking a look at what the best fix would be.

[vantezzen]

@kytwb The problem should be fixed by 1b18a7b, can you take a look?

[kytwb]

Will ship when closing https://github.com/kytwb/ferdi/issues/23.

[PandaWhisperer]

I changed all "Fanz" occurrences in ~.config/Ferdi/recipes/whatsapp/index.js to "Ferdi" and now it works great :)

This worked for me, or at least it did once I figured out that on MacOS, this file is located at ~/Library/Application Support/Ferdi/recipes/whatsapp/index.js.

[kytwb]

@PandaWhisperer do you still need this manual fix with the latest version?

[PandaWhisperer]

@kytwb I am on 5.3.0, installed about a week ago via Homebrew. As far as I can tell, that is the latest version (in-app update checks confirms this).

[vantezzen]

@PandaWhisperer The newest version is 5.3.3, this bug should be fixed in 5.3.1+ (although you sometimes need to reload WhatsApp using CMD+R to work).
Can you try updating the cask via Homebrew or manually upgrading Ferdi?

Unfortunately, the build-in updater won't work until the next Ferdi release as this requires the application to be signed by Apple, which we are only currently adding (see #35)

[PandaWhisperer]

@vantezzen I tried both, but neither the in-app update checker or brew cask outdated is reporting any available updates to install.

Also, since I just manually fixed it, I don't suppose installing newer version of Ferdi would overwrite those changes? I assume the config directory is only created once, when Ferdi is started for the first time.

[vantezzen]

Ferdi won't overwrite the WhatsApp recipe but v5.3.1 added the fix directly to Ferdi's code and uses is across all services.

[PandaWhisperer]

@vantezzen gotcha. So while Ferdi still doesn't show up when I run brew cask outdated, I do seem to be able get the newest version by running brew cask upgrade ferdi.

It's downloading 5.3.3 right now. Perhaps brew cask outdated is broken, or casks just work differently?

[vantezzen]

brew cask outdated shows a list of outdated casks that do not auto-update themselves. Ferdi however, does auto-update and thus doesn't get shown.
You'll have to run brew cask outdated --greedy in order to see if Ferdi is outdated.

https://github.com/getferdi/ferdi/issues/61#issuecomment-533778359

[SMile61]

I had the problem today. Replacing Franz occurences by Ferdi in the recipe is still working.
Thanks for the solution
W10/Ferdi 5.4.3