Bug 466493

Summary:	crashes when given invalid url
Product:	[Applications] kasts	Reporter:	aschonforums
Component:	general	Assignee:	bart
Status:	RESOLVED WORKSFORME
Severity:	crash
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Android
OS:	Android 13.x
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description aschonforums 2023-02-26 22:49:13 UTC

SUMMARY

added an rss feed with an invalid url by accident and kasts crashed
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.navigate to "add podcast"
2. add invalid podcast link (in this case https://exiledonline.com/45wn84klrz/RSS which gives a 404 in the browser, the correct link ends in feed.xml)

OBSERVED RESULT
kasts crashed, when i tried to reopen it crashed again immediately

EXPECTED RESULT
a message saying something like "invalid url"

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 bart 2023-02-27 07:11:28 UTC

Mmm, strange.  I can't seem to reproduce this.
Both on linux and android, I'm getting the expected "Podcast update error".  The app doesn't crash for me.

On a related note: I did notice that the android version is prone to random crashes which don't happen on other platforms.  If I have some time I'll try and look into this.

Comment 2 bart 2023-03-10 15:30:19 UTC

I still can't reproduce this. Could you perhaps check if it's still happening with the latest build for you?

Comment 3 aschonforums 2023-03-12 17:51:13 UTC

(In reply to bart from comment #2)
> I still can't reproduce this. Could you perhaps check if it's still
> happening with the latest build for you?

it isn't happening anymore with the newest build from the binary factory.

Comment 4 bart 2023-03-14 14:48:34 UTC

Thanks for checking again.  I'll close this bug report.  Feel free to reopen if it would reoccur.