Cannot add MyAnimeList tracking

N0153 commented 8 months ago

Steps to reproduce

Go to Settings -> Tracking
Click on MyAnimeList
Log in to MyAnimeList
Click on the Allow button
(Optional) Use Fingerprint/Insert PIN after being redirected to Mihon

Expected behavior

The MyAnimeList tracker should be successfully registered to Mihon (the green checkmark should be visible next to the MyAnimeList tracker).

Actual behavior

The MyAnimeList tracker is not registered to Mihon (no green checkmark appears next to the MyAnimeList tracker).

Crash logs

No response

Mihon version

0.16.3

Android version

Android 13

Device

Asus ZenFone 9 (ASUS_AI2202)

Other details

No response

Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 0.16.3.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Nachogao commented 8 months ago

I has the same problem, but I resolved it closing the app, and doing it again. And now I cannot reproduce the error.

N0153 commented 8 months ago

I has the same problem, but I resolved it closing the app, and doing it again. And now I cannot reproduce the error.

After trying multiple times, I finally managed to get the green checkmark on MyAnimeList. The problem is that, when I try to update any entry I get a "HTTP error 403" message, followed by an "HTTP error 503" message shortly after.

After a while I managed to make the application crash somehow. Following you will find the error.log

App version: 0.16.3 (standard, 139663a, 4, 2024-01-29T20:34Z)
Android version: 13 (SDK 33; build TKQ1.220807.001.33.0804.2060.218 release-keys)
Device brand: asus
Device manufacturer: asus
Device name: ASUS_AI2202 (EU_AI2202)
Device model: ASUS_AI2202
WebView: Android System WebView 122.0.6261.5

--------- beginning of main
01-31 22:56:29.136 22222 22222 E app.mihon: Not starting debugger since process cannot load the jdwp agent.
01-31 22:56:29.230 22222 22260 E SQLiteLog: (283) recovered 21 frames from WAL file /data/data/app.mihon/databases/tachiyomi.db-wal
01-31 22:56:29.331 22222 22283 E chromium: [0131/225629.330903:ERROR:variations_seed_loader.cc(37)] Seed missing signature.
01-31 22:56:30.077 22222 22403 E SQLiteLog: (284) automatic index on C(manga_id)
01-31 22:56:30.077 22222 22403 E SQLiteLog: (284) automatic index on mangas_categories(manga_id)
--------- beginning of crash
01-31 22:56:41.307 22222 22222 E AndroidRuntime: FATAL EXCEPTION: main
01-31 22:56:41.307 22222 22222 E AndroidRuntime: Process: app.mihon, PID: 22222
01-31 22:56:41.307 22222 22222 E AndroidRuntime: android.os.BadParcelableException: Parcelable encountered IOException writing serializable object (name = eu.kanade.tachiyomi.ui.manga.track.TrackChapterSelectorScreen)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeSerializable(Parcel.java:2751)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2517)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2316)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeList(Parcel.java:1382)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2460)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2316)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeList(Parcel.java:1382)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2460)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2316)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeMapInternal(Parcel.java:1233)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeMap(Parcel.java:1215)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2430)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2316)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeMapInternal(Parcel.java:1233)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeMap(Parcel.java:1215)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2430)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2316)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeList(Parcel.java:1382)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2460)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2316)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeArrayMapInternal(Parcel.java:1265)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.BaseBundle.writeToParcelInner(BaseBundle.java:1809)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Bundle.writeToParcel(Bundle.java:1365)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeBundle(Parcel.java:1334)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2433)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2323)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeArrayMapInternal(Parcel.java:1265)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.BaseBundle.writeToParcelInner(BaseBundle.java:1809)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Bundle.writeToParcel(Bundle.java:1365)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeBundle(Parcel.java:1334)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2433)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeValue(Parcel.java:2323)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.BaseBundle.dumpStats(BaseBundle.java:1881)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.BaseBundle.dumpStats(BaseBundle.java:1918)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.app.servertransaction.PendingTransactionActions$StopInfo.run(PendingTransactionActions.java:150)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Handler.handleCallback(Handler.java:942)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Handler.dispatchMessage(Handler.java:99)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Looper.loopOnce(Looper.java:241)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Looper.loop(Looper.java:358)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.app.ActivityThread.main(ActivityThread.java:8114)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at java.lang.reflect.Method.invoke(Native Method)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:942)
01-31 22:56:41.307 22222 22222 E AndroidRuntime: Caused by: java.io.NotSerializableException: tachiyomi.domain.track.model.Track
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1240)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1620)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1581)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1490)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1234)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:354)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    at android.os.Parcel.writeSerializable(Parcel.java:2746)
01-31 22:56:41.307 22222 22222 E AndroidRuntime:    ... 42 more
01-31 22:56:50.917 22768 22768 E n:error_handler: Not starting debugger since process cannot load the jdwp agent.
01-31 22:56:51.005 22768 22791 E SQLiteLog: (283) recovered 6 frames from WAL file /data/data/app.mihon/databases/tachiyomi.db-wal

vitorggois commented 8 months ago

I has the same problem, but I resolved it closing the app, and doing it again. And now I cannot reproduce the error.

After trying multiple times, I finally managed to get the green checkmark on MyAnimeList. The problem is that, when I try to update any entry I get a "HTTP error 403" message, followed by an "HTTP error 503" message shortly after.

I'm having the same issue with HTTP errors

loocool2 commented 8 months ago

MAL is still blocking the manga endpoints in the MAL api as of about 12h ago

N0153 commented 8 months ago

MAL is still blocking the manga endpoints in the MAL api as of about 12h ago

Thanks! I cannot access the MAL Discord at the moment. Are there any updates on this issue?

By the way, a few minutes ago I tried to update the tracking on some manga again. This time I didn't get an error (neither a 403 nor a 503), but the tracking still didn't update.

loocool2 commented 8 months ago

No change since that

KyunnDayo commented 8 months ago

02/02/24- issue still reproducible with mal error 503

ultrabear commented 8 months ago

getting the same issue as originally stated too

xifutang commented 8 months ago

Thought it was just me lol

MajorTanya commented 8 months ago

Thank you all for the reports but please refrain from adding things like "me too" as comments. If you want to signal you're also affected by this, just click the 👍 emoji on the original issue at the top. A lot of people get emails from issues and getting one just to see "happened to me as well" is not the vibe. Again, thanks for the reports but stick to the emoji reaction 👍

dgw commented 8 months ago

Comment 38 in a related thread on MAL's forum indicates that while the related API functionality seems to be restored, Mihon itself is potentially blocked by user-agent. https://myanimelist.net/forum/?goto=post&topicid=2143705&id=70563666

Presumably that would need a Mihon developer to reach out and see what (if anything) MAL needs to unblock it.

etreff commented 8 months ago

Comment 38 in a related thread on MAL's forum indicates that while the related API functionality seems to be restored, Mihon itself is potentially blocked by user-agent. https://myanimelist.net/forum/?goto=post&topicid=2143705&id=70563666

Presumably that would need a Mihon developer to reach out and see what (if anything) MAL needs to unblock it.

MAL is notorious for being extremely difficult to work with, both from a user perspective and a developer perspective. Mihon would absolutely need to reach out to MAL to resolve this, but I do not expect much. One thing to keep in mind is that while MAL is a tracker they also sell digital copies of licensed manga. They probably wouldn't be too keen on working with an app that easily enables sidestepping their business.

Atsuya12 commented 8 months ago

Guys, I don't know if this changed to someone else, but my MAL tracking is working again. I'm currently running the Beta r6501 version of the app

MajorTanya commented 8 months ago

Guys, I don't know if this changed to someone else, but my MAL tracking is working again. I'm currently running the Beta r6501 version of the app

We're aware of this, but there are still some blockers on the main version.

N0153 commented 8 months ago

Guys, I don't know if this changed to someone else, but my MAL tracking is working again. I'm currently running the Beta r6501 version of the app

We're aware of this, but there are still some blockers on the main version.

I can confirm this. I just unregistered the MAL tracker (it wasn't working anyway) and tried to add it again from scratch, but it seems I'm back to square one, as I couldn't even register the tracker with Mihon (no green tick next to the tracker name).

KyunnDayo commented 8 months ago

02/16/24 running mihon stable 0.16.3

myanimelist tracking seems to be working now

N0153 commented 8 months ago

02/16/24 running mihon stable 0.16.3

myanimelist tracking seems to be working now

I just checked it myself. I can also confirm that it is working fine at the moment.

SoumickDeyArgha commented 7 months ago

Using Mihon stable 0.16.3

02/16/24 running mihon stable 0.16.3

myanimelist tracking seems to be working now

I have tried everything from scratch, but still it's not working for me as of 17/02/24.

Smol-Ame commented 7 months ago

Using Mihon stable 0.16.3

02/16/24 running mihon stable 0.16.3 myanimelist tracking seems to be working now

I have tried everything from scratch, but still it's not working for me as of 17/02/24.

It seems like another MAL-related issue as of about 6 hours ago (when I first saw it), nothing you can do but wait

dgw commented 7 months ago

That forum thread I linked before is active again with more problem reports.

I really hope the MAL team will make a statement about this, but if they are still targeting specific clients/UAs then it's probably intentional.

MajorTanya commented 7 months ago

Only reopening so people find this easier, I don't want to see any "+1" or "me too" or "when is this getting fixed???!1!??"

We know as much as you do when it comes to the reasoning behind this.

Th3-822 commented 7 months ago

maybe there are lots of users retrying as while it's blocked it justs gets timeout on mihon instead of returning a real error code, like 403, 429 or 503 while its blocked (it returns 504 iirc after 120 seconds and mihon doesn't wait that much for the reply)

increasing the timeout and maybe adding a forced logout if there is a error updating to just stop sending invalid requests as maybe there are some users still using expired/invalid tokens (from "old" backups) without noticing it

or just allowing to customize the useragent for the trackers (and maybe api's appid & public/secret tokens too) to be able to avoid any future block

MajorTanya commented 7 months ago

maybe there are lots of users retrying as while it's blocked it justs gets timeout on mihon instead of returning a real error code, like 403, 429 or 503 while its blocked (it returns 504 iirc after 120 seconds and mihon doesn't wait that much for the reply)

increasing the timeout and maybe adding a forced logout if there is a error updating to just stop sending invalid requests as maybe there are some users still using expired/invalid tokens (from "old" backups) without noticing it

or just allowing to customize the useragent for the trackers (and maybe api's appid & public/secret tokens too) to be able to avoid any future block

504 is literally just a timeout message (meaning the server didn't respond at all), and no well-behaved API takes longer than Mihon is waiting, especially not 120 seconds/2 full minutes. (see below for an educational illustration)
Allowing for UA replacements for trackers would be a pretty fundamental change to the structure of the code, and I don't know if it would even be API Licence/ToS compliant to allow for it in the first place
Users should stop trying if the tracker isn't responding
Further optimisations (& suggestions) on Mihon's end to maybe curtail some of the issues are always welcome, but no viable ideas have been floated thus far, and MAL doesn't appear to be communicating with anyone, let alone Mihon

breddiesucks commented 7 months ago

Recently migrated from Tachiyomi to Mihon. I was able to get the MAL token, but I noticed that MAL isn't tracking the progress. On further fiddling, I noticed that anything MAL related isn't working with Mihon. Now I tried re-enabling the token but now I get this "400 Bad Request" error. wtf is MAL doing with these apps, didn't Mihon specifically remove pre-configured extension list to avoid legal issues?

BraveSoldat commented 7 months ago

Recently migrated from Tachiyomi to Mihon. I was able to get the MAL token, but I noticed that MAL isn't tracking the progress. On further fiddling, I noticed that anything MAL related isn't working with Mihon. Now I tried re-enabling the token but now I get this "400 Bad Request" error. wtf is MAL doing with these apps, didn't Mihon specifically remove pre-configured extension list to avoid legal issues?

I don't think this is limited to Mihon. I use PocketMAL for manually tracking anime and physical manga I read and I had some trouble with it when this API problem began. Sometimes PocketMAL still has some connection issues with MAL, so it isn't really normalized yet. I guess MAL began monitoring their API usage requests more closely and are trying to make third parties lower the rate of requests. Hence the API usage notice Mihon devs received from MAL. If devs don't comply, then MAL resorts to more drastic measures.

That's just my guess though.

breddiesucks commented 7 months ago

Recently migrated from Tachiyomi to Mihon. I was able to get the MAL token, but I noticed that MAL isn't tracking the progress. On further fiddling, I noticed that anything MAL related isn't working with Mihon. Now I tried re-enabling the token but now I get this "400 Bad Request" error. wtf is MAL doing with these apps, didn't Mihon specifically remove pre-configured extension list to avoid legal issues?

I don't think this is limited to Mihon. I use PocketMAL for manually tracking anime and physical manga I read and I had some trouble with it when this API problem began. Sometimes PocketMAL still has some connection issues with MAL, so it isn't really normalized yet. I guess MAL began monitoring their API usage requests more closely and are trying to make third parties lower the rate of requests. Hence the API usage notice Mihon devs received from MAL. If devs don't comply, then MAL resorts to more drastic measures.

That's just my guess though.

Thanks man. Sorry for being a dick. For one thing, I know MAL isn't actually very good in server stability department, but trying to restrict API calls is scummy man. If MAL wants people to use their shitass app, they should make it function better than their FOSS counterparts. If shit starts hitting the ceiling, I think it's time to consider Anilist (let it be however I loved MAL's classic image board style forums).

Smol-Ame commented 7 months ago

They were specifically blocking Mihon for the past couple days, but from what I've been seeing tonight, their API might be down again

Appoxo commented 7 months ago

Juat tried it with Tachiyomi (0.15.3) and Mihon (0.16.3) on Pixel 7 Pro (Android 14)

Tachiyomi worked first try Mihon loaded forever

SoumickDeyArgha commented 7 months ago

Tried with Tachiyomi today I did changes the user agent and it's work like a charm.

Mozilla/5.0 (Linux; Android 13) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/20.0 Chrome/106.0.5249.126 Mobile Safari/537.36

Appoxo commented 7 months ago

Tried with Tachiyomi today I did changes the user agent and it's work like a charm.

Mozilla/5.0 (Linux; Android 13) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/20.0 Chrome/106.0.5249.126 Mobile Safari/537.36

You mean you changed the Mihon user agent or the tachiyomi one?

SoumickDeyArgha commented 7 months ago

Tried with Tachiyomi today I did changes the user agent and it's work like a charm. Mozilla/5.0 (Linux; Android 13) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/20.0 Chrome/106.0.5249.126 Mobile Safari/537.36

You mean you changed the Mihon user agent or the tachiyomi one?

Tachiyomi Worked with chage User agent Mihon didn't I tried different user agent but nothing working

SoumickDeyArgha commented 7 months ago

They were specifically blocking Mihon for the past couple days, but from what I've been seeing tonight, their API might be down again

If that's then case, then some user mentioned the Mal tracking working in Mihon preview, idk what could be thr reason behind it

MajorTanya commented 7 months ago

Users can't influence the User-Agent Mihon uses for MAL. And I'm 90% sure the preview doesn't work either because of how MAL is blocking Mihon.

Appoxo commented 7 months ago

They were specifically blocking Mihon for the past couple days, but from what I've been seeing tonight, their API might be down again

If that's then case, then some user mentioned the Mal tracking working in Mihon preview, idk what could be thr reason behind it

Tried it yesterday with the newest release. Either it doesnt work or I was too impatient.

MajorTanya commented 7 months ago

They were specifically blocking Mihon for the past couple days, but from what I've been seeing tonight, their API might be down again

If that's then case, then some user mentioned the Mal tracking working in Mihon preview, idk what could be thr reason behind it

Tried it yesterday with the newest release. Either it doesnt work or I was too impatient.

It doesn't work at all for any Mihons right now

dgw commented 7 months ago

7974a1fc0c2b0e237d5704a033a60ec0fd60cdbc being included in 0.16.4 released earlier today sounded like it would make MAL auth/tracking work again, but I'm still getting timeouts. Is there another step to this besides updating the Mihon app? Maybe a cache to clear?

Fuuzetsu commented 7 months ago

I also confirm no improvement on r6530, just getting the spinner.

Smol-Ame commented 7 months ago

7974a1f being included in 0.16.4 released earlier today sounded like it would make MAL auth/tracking work again, but I'm still getting timeouts. Is there another step to this besides updating the Mihon app? Maybe a cache to clear?

I also confirm no improvement on r6530, just getting the spinner.

For the both of you, please change your default user-agent (Mihon Settings > Advanced) to something else. Then it should work

dgw commented 7 months ago

@Smol-Ame Thanks, that was the missing step. Made a few tweaks to the UA string and I was then able to add MAL back in the Tracking settings :tada:

vitorggois commented 7 months ago

For the both of you, please change your default user-agent (Mihon Settings > Advanced) to something else. Then it should work

Tried a bunch of user-agents that I found on the troubleshoot link, still got nothing. Anyone can tell me an user-agent that worked?

SoumickDeyArgha commented 7 months ago

For the both of you, please change your default user-agent (Mihon Settings > Advanced) to something else. Then it should work

Tried a bunch of user-agents that I found on the troubleshoot link, still got nothing. Anyone can tell me an user-agent that worked?

You can try this one Mozilla/5.0 (Linux; Android 13) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/20.0 Chrome/106.0.5249.126 Mobile Safari/537.36

Appoxo commented 7 months ago

For the both of you, please change your default user-agent (Mihon Settings > Advanced) to something else. Then it should work

Tried a bunch of user-agents that I found on the troubleshoot link, still got nothing. Anyone can tell me an user-agent that worked?

If I try tobauth, Mihin open the native Firefix App. So idk if it matters. Anyway, heres mine: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/120.0

Smol-Ame commented 7 months ago

For the both of you, please change your default user-agent (Mihon Settings > Advanced) to something else. Then it should work

Tried a bunch of user-agents that I found on the troubleshoot link, still got nothing. Anyone can tell me an user-agent that worked?

Just checking, you did restart the app after applying a user-agent, right?

vitorggois commented 7 months ago

Just checking, you did restart the app after applying a user-agent, right?

Every time I changed something I restarted.

BraveSoldat commented 7 months ago

It's working for me with this UA:

Mozilla/5.0 (Linux; Android 13) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/20.0 Chrome/106.0.5249.126 Mobile Safari/537.36

vitorggois commented 7 months ago

Reinstalled the whole app, seems to be working now.

Doministo commented 7 months ago

For the both of you, please change your default user-agent (Mihon Settings > Advanced) to something else. Then it should work

Tried a bunch of user-agents that I found on the troubleshoot link, still got nothing. Anyone can tell me an user-agent that worked?

If I try tobauth, Mihin open the native Firefix App. So idk if it matters. Anyway, heres mine: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/120.0

To be honest I just changed Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/121.0 to Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/120.0 and then it worked, so nice and thanks yall

mihonapp / mihon