-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add cross-instance functionality #14
Comments
This is almost done - however, at the moment the custom instance URL isn't being loaded in time; still trying to figure out a solution to this |
This has now been added; you can specify a custom instance, and once the app is reopened it will connect to it - however, it's a bit clunky (you have to reopen the app after changing the URL) and the support is pretty basic so I'm not 100% sure whether I want to enable this by default in the next version |
Hey, thank you guys for adding it :) Not sure why this is now the only client that supports multi instance, but it's a start! Also, why'd you guys rebase off of my fork 😅 Not mad or anything, I just think it's funny how I'm now technically a contributor (even though I basically didn't do anything) |
You bumped a bunch of deps at one point and had a much more extensive README; I think at the time I wanted to save some time (as I was also unsure as to whether I was going to continue maintaining the project in a fork or here) |
I don't remember changing any deps, I think I just ran |
I suspect it might not've logged in properly, although I'll have to do further debugging; however, last time I tried to set up a Divolt account it seemingly just kept erroring so hmm |
If it was a database error, it's Divolt's side. There's some bug in the DB that sometimes causes it to crash. We just have it on an hourly restart for now. (Of course, it's good to check if you're able to login on the website first) |
I managed to log in without any issues on a test account so hmmm |
Reloads work? |
? |
Thank you. I'm getting a different error now, though. This one occurs on the login screen regardless of restarts. Tried reinstall too. Not sure why this is occuring, might try it on WSA later.
Basically, yeah. Since RVMob now supports instance switching, we'll probably stop working on DVMob and recommend people to use this instead. |
That error seems to be related to certificates - I haven't seen it locally so it might be a Divolt issue but I'm not 100% sure
Sounds good ^^ |
Wouldn't an easy fix, be to explicitely disable any certificate pinning? Then you don't have to worry about certificate errors, as it'd then fallback to whatever the os or user ended up trusted. |
In-case you were thinking of publishing RVMob to the play store, I even searched to see if omitting client certificate pinning would stop it from getting approved, and seems it's not a requirement, and even discouraged to be used as a solution according to this article: |
RVMob doesn't pin any certificates directly so I'm not sure where this issue is coming from |
I think it was, I'm not getting it anymore, both on WSA and on my Note 10. Maybe the spaghetti code somehow fixed itself or the hourly restart fixed it, idk... Subsequent restarts do work, though, so at least that's fixed :D |
I'm gonna close this issue as completed. The final polishing work will be listed in another issue; if you encounter any issues, either open another issue or let me know in the RVMob server |
What do you want to see?
Add a rudimentary form of switching the API path used by the app, so situations like this don't need to occur.
The text was updated successfully, but these errors were encountered: