-
Notifications
You must be signed in to change notification settings - Fork 221
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
import apprise module #2497
Comments
This issue has been fixed in beta.38. I don't what version you are running but I suggest you keep your config directory but empty the content of your Bazarr directory and extract the latest bazarr.zip asset to start new (https://github.com/morpheus65535/bazarr/releases/download/v1.4.3-beta.38/bazarr.zip). |
I deleted my bazarr and downloaded the latest beta. Then I get this error:
When I close my terminal and try to run Bazarr again I get the same message:; |
What operating system? Python version? Using venv or not? |
Using macOS 14 certifi 2024.2.2 |
What is the value of general-->branch in your config.yaml file? |
its says master. |
So development branch that you unzip get overwritten by master on first start. Change the value to |
Here a weird one. I removed everything of Bazarr. Downloaded the master v1.4.2 release. Everything works. In settings - general in the UI I change the branch to development. I did the Bazarr task update and same problems appears. So even with a new master installation and changing and updating to the development branch, the same Apprise problem.
The branch in config.yaml is development |
What's the content of |
I downloaded the beta again and placed those two files in the folder. That worked for me! Somehow the update mechanism deleted these 2 files (for me) somehow but now it works! |
I hope it will be fixed in upcoming beta. I'll run some test and see if it's safe to merge dev to master. |
…rst. 1.8.0 will get back in nightly shortly. #2497
This one has been fixed. |
I updated to latest beta of Bazarr [v1.4.3-beta.38] and it doesn't start anymore.
Using Python v3.11.6
The text was updated successfully, but these errors were encountered: