Am I missing something or is there no youtube player in the official Jolla store?
If indeed there is no youtube player in the Jolla store, why is that?
I saw players in other stores, so they definitely exist.
Just don’t use jolla store. nobody uses it it has no apps
2 Likes
And here is the list of reasons why if you want to know:
Package name
============
65872 blocks
ERROR [microtube] Name is not valid. Must start with 'harbour-', matching '^harbour-[-a-z0-9_\.]+$'.
INFO [microtube] Please see our FAQ here: https://harbour.jolla.com/faq#Naming
FAILED
RPM file name
=============
WARNING [microtube-3.8.6-1.aarch64.rpm] rpm file name can not be verified for sure ('Package name' check failed), ensure it to be: harbour-name-version-release.architecture.rpm
PASSED
QML files
=========
INFO [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/pages/components/private/QuickScrollButton.qml] Uses Sailfish Silica Components (only reported once)
ERROR [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/pages/components/private/QuickScrollButton.qml] Import 'Sailfish.Silica.private 1.0' is not allowed
ERROR [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/pages/components/private/HighlightImage.qml] Import 'Sailfish.Silica.private 1.0' is not allowed
ERROR [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/pages/components/SilicaFastListView.qml] Import 'Sailfish.Silica.private 1.0' is not allowed
ERROR [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/pages/components/SharePage.qml] Import 'Sailfish.TransferEngine 1.0' is not allowed
ERROR [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/pages/VideoPlayer.qml] Import 'org.nemomobile.mpris 1.0' is not allowed
ERROR [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/pages/VideoPlayer.qml] Import 'com.jolla.settings.system 1.0' is not allowed
ERROR [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/pages/VideoPlayer.qml] Import 'org.nemomobile.systemsettings 1.0' is not allowed
WARNING [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/pages/VideoPlayer.qml] Import 'org.nemomobile.configuration 1.0' is deprecated
WARNING [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/pages/UpdateDialog.qml] Import 'org.nemomobile.configuration 1.0' is deprecated
WARNING [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/pages/SponsorBlockSettings.qml] Import 'org.nemomobile.configuration 1.0' is deprecated
WARNING [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/pages/Settings.qml] Import 'org.nemomobile.configuration 1.0' is deprecated
WARNING [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/pages/Main.qml] Import 'org.nemomobile.configuration 1.0' is deprecated
WARNING [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/pages/InstallDialog.qml] Import 'org.nemomobile.configuration 1.0' is deprecated
WARNING [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/microtube/qml/microtube.qml] Import 'org.nemomobile.configuration 1.0' is deprecated
INFO [microtube] Please see our FAQ here: https://harbour.jolla.com/faq#QML_API
FAILED
Desktop file
============
ERROR [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/applications/microtube.desktop] X-Sailjail key is not allowed: Sandboxing
INFO [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/applications/microtube.desktop] Please see our FAQ here: https://harbour.jolla.com/faq#.desktop-Files
FAILED
Paths
=====
INFO [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/icons/hicolor/[0-9x]{5,9}/apps/microtube.png] All needed icons found!
ERROR [/home/foidbgen/Programs/SailfishOS/mersdk/targets/SailfishOS-5.0.0.62-aarch64.default/usr/share/applications/microtube-url.desktop] Installation not allowed in this location
FAILED
Oh also sailjail with internet permission doesn’t allow internet access so thats also something to be fixed by jolla thats not fixed yet.
Jolla can fix their store any time they want but they refuse to and i’m not going to hack my app around to fit it in their store.
Also I’m the only one that should answer here because there’s only one youtube client xd
2 Likes
I have many questions.
Who owns/maintains sailjail?
Generally speaking, who owns/maintains all those Sailfish APIs which are not allowed in the store?
I assumed every Sailfish API is owned/maintained by Jolla, but everything is unclear and almost all Jolla employees on the forum are not helpful at all when I ask any complicated questions.
How can a Sailfish API even be owned/maintained by someone else than Jolla?
Other than being unstable, what other reasons are there for refusing APIs in the Jolla store?
Can a youtube player be implemented without the forbidden APIs that you used?
Did you use them because it was easier, or is there actually no equivalent functionality provided officially by Jolla?
Jolla, with upstream being firejail which is not maintained by jolla
Thats it. General idea is for apps in jolla store to not break with updates. if api is unstable and can introduce breaking changes like dialer api which is used in my yottagram, that would break compatibility and break apps.
Maybe, maybe not. But I’m done with repeatedly extending my hand to jolla just for it to be slapped or set on fire. They don’t want my apps? Their loss cause if someone wants my app they’ll install it. And there’s nothing wrong with my app it works perfectly, its problem with jolla store.
latter. You could hack in some by compiling libraries you’re using with the app but its bothersome and stupid. but not all.
3 Likes
Jolla breaks at least one of my apps every release and its actually more rare for them not to break my apps. All it would take to avoid it is for them to launch microtube once and check if video is playing. Of course its not viable to test every app but i’m talking about couple most used apps. but no, why bother. Nobody at jolla actually uses sfos apps. They’re just using android or iphones or android via aliendalvik. Even Sami has literally no salifish apps only android ones. with that attitude no wonder. They are actively fighting developers and don’t allow their apps in their store. No wonder people just give up on developing apps with that attitude.
Sorry had to get it off my chest and this place might be good enough for that
13 Likes
It is simple:
- OpenRepos allows app developers to use a lot of different functions / libraries, etc. outside of Jollas Sailfish API for instance or APIs which are often changed, etc.
- Chum does allow more than Jollas store itself too.
- Jolla’s own app store does only allow very limited functionalities and is very strict in what is allowed and what is not allowed to be done.
Think of it like a Playlist. The owners likes some titles, but do not like others.
Jolla owns it’s own Playlist and can do whatever they want with it.
“Jolla Store” is a very picky playlist creator and even if you ask them to put your song onto their playlist they often refuse it – lets say they only like classical music. Most often not because the other music would be bad but because they do not have the time to listen to it very closely and will just refuse it just in case.
Chum & OpenRepos are other Playlist owners, which is less strict and likes classical music / rap / hard rock / and pop.
Or in other terms:
If a developer want to use a functionality / library / API combination, which is not allowed / whitelisted by Jolla, the app will not be let into the Jolla store itself but may very well be allowed in OpenRepos.
Meaning:
If you want to make sure you are absolutely not downloading something that is somehow harmful (let’s say no erotic content whatsoever, no finger print reader used in the app and it will absolutely not break with the next update, etc): Use Jollas Store.
If you like a pretty solid security level, go to Chum & OpenRepos or depending on if you have Android App Support: You can use F-Droid.
Have a look at this page about what I recommend and why:
https://www.patchwork3d.de/sailfish-os-249-en
4 Likes
Thank you for the details!
Yeah basically i could craft package that would remove all your files basically rm -rf on install and i can publish that in openrepos and chum but not jolla store cause human checks packages in jolla store
3 Likes
I assume Sami is the CEO of Jolla.
I really hope you are wromg about him using mostly android apps.
Do you really know this to be true? Or are you just venting? (I also vent like that myself, tbh)
If you really do know that for a fact, how did you find out such a thing?
I met him couple years back and saw his xperia xd
3 Likes
And yes, he had to vent a little bit too… and that is fine from time to time. 
Hey, jolla ceo’s phone number is my one of the most priced possessions xd
You may want to ask him if he uses Android apps because he doesnt like SFOS apps or if it at least sometimes has to do with his work: He has to make sure that Android apps work on AD / Appsupport while he is likely very confident that you are doing a great job anyway.
1 Like
I am still confused about the Whole API situation.
Does Jolla forbid some of their own APIs like sailjail in their own store?
I can understand forbidding some third-party libraries, but what is the point in forbidding your own APIs?
Is it because they have APIs which they made public before they were ready and now they have stopped working on them?
If so, why not remove the APIs completely?
Is it because they are still working on them or hoping to work on them some time in the future when they will have more resources?
Or do they only forbid some generic Linux APIs?
What is going on?
no jolla requires sailjail while its broken so i don’t use it
more like they’re actively working on them so api can change any time
this one
1 Like
Cool, thanks for the clarification!
What you are describing doesn’t sound fundamentally wrong to me.
I mean, as long as they are still working on sailjail, it will eventually get fixed, right?
sure…
like the 5 years old bugs
3 Likes
Just when he was confident again you pushed him over the cliff.
5 Likes
May i remind everyone of app settings that are all nicely in one place in settings except you’re not allowed to add your app’s settings there if you want to add app to jolla store
that issue exists since sailfishos was created and was not addressed to this day.
4 Likes