[Bug] Bilibili search engine glitch

[Rolling127]

Checklist (Your issue will be automatically closed if you delete this part)

• I make sure that there are no existing issues - open or closed - which I could contribute my information to.
• I understand that issues with limited impact, such as those occurring on specific devices or under specific network conditions, will not be fixed.
• I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
• I have attached the error report in the issue.

Describe the bug
You sometimes need to try several times to make the search engine works.

Frequency Sometimes

Steps to reproduce the bug
Search something on Bilibili and it may will happen.

Device (e.g. Pixel 9 Pro)
SAMSUNG A34 5G

Error report

Exception

• User Action: get suggestions
• Request:
• Content Country: US
• Content Language: en
• App Language: en
• Service: BiliBili (Anonymous)
• Version: 4.4.2
• OS: Linux samsung/a34xzh/a34x:14/UP1A.231005.007/A3460ZHU9CXK1:user/release-keys 14 - 34

Crash log

org.schabi.newpipe.extractor.exceptions.ReCaptchaException: reCaptcha Challenge requested
	at org.schabi.newpipe.DownloaderImpl.execute(DownloaderImpl.java:274)
	at org.schabi.newpipe.extractor.downloader.Downloader.get(Downloader.java:86)
	at org.schabi.newpipe.extractor.downloader.Downloader.get(Downloader.java:63)
	at org.schabi.newpipe.extractor.services.bilibili.extractors.BilibiliSuggestionExtractor.suggestionList(BilibiliSuggestionExtractor.java:26)
	at org.schabi.newpipe.util.ExtractorHelper.lambda$suggestionsFor$2(ExtractorHelper.java:118)
	at org.schabi.newpipe.util.ExtractorHelper$$ExternalSyntheticLambda14.call(Unknown Source:4)
	at io.reactivex.rxjava3.internal.operators.single.SingleFromCallable.subscribeActual(SingleFromCallable.java:43)
	at io.reactivex.rxjava3.core.Single.subscribe(Single.java:4813)
	at io.reactivex.rxjava3.internal.operators.single.SingleToObservable.subscribeActual(SingleToObservable.java:36)
	at io.reactivex.rxjava3.core.Observable.subscribe(Observable.java:13131)
	at io.reactivex.rxjava3.internal.operators.observable.ObservableMap.subscribeActual(ObservableMap.java:33)
	at io.reactivex.rxjava3.core.Observable.subscribe(Observable.java:13131)
	at io.reactivex.rxjava3.internal.operators.observable.ObservableZip$ZipCoordinator.subscribe(ObservableZip.java:110)
	at io.reactivex.rxjava3.internal.operators.observable.ObservableZip.subscribeActual(ObservableZip.java:72)
	at io.reactivex.rxjava3.core.Observable.subscribe(Observable.java:13131)
	at io.reactivex.rxjava3.internal.operators.observable.ObservableMaterialize.subscribeActual(ObservableMaterialize.java:28)
	at io.reactivex.rxjava3.core.Observable.subscribe(Observable.java:13131)
	at io.reactivex.rxjava3.internal.operators.observable.ObservableSwitchMap$SwitchMapObserver.onNext(ObservableSwitchMap.java:127)
	at io.reactivex.rxjava3.internal.operators.observable.ObservableConcatMap$ConcatMapDelayErrorObserver$DelayErrorInnerObserver.onNext(ObservableConcatMap.java:499)
	at io.reactivex.rxjava3.observers.SerializedObserver.onNext(SerializedObserver.java:114)
	at io.reactivex.rxjava3.internal.operators.observable.ObservableDebounceTimed$DebounceTimedObserver.emit(ObservableDebounceTimed.java:143)
	at io.reactivex.rxjava3.internal.operators.observable.ObservableDebounceTimed$DebounceEmitter.run(ObservableDebounceTimed.java:168)
	at io.reactivex.rxjava3.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:65)
	at io.reactivex.rxjava3.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:56)
	at java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:307)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
	at java.lang.Thread.run(Thread.java:1012)

---

Additional context
I only tested it on the latest debug version.
Important update:Now it works just fine.

[InfinityLoop1308]

https://www.ithome.com/0/860/436.htm It's BiliBili's server issue.

[Rolling127]

https://www.ithome.com/0/860/436.htm這是BiliBili的伺服器問題。

OK, thanks for the reply