On Saturday 05 April 2014 18:02 Kaj-Michael Lang wrote: > Hi > > Got denied application update as I set my org name properly with > app->setOrganizationName() but that lead to a application update > rejection as then the path given from > QStandardPaths::writableLocation(QStandardPaths::CacheLocation) > > is not in the format harbour likes. After much digging and finally > looking into SailfishApp sources it seems that I'm not even supposed to > set the orgname myself, as it sets, unlogicaly, the orgname to appname, > and in my mind that feels a a bit strange. > > Anyway, this took a while for me to find out and it is not mentioned in > the harbour FAQ, might be good to add it.
This sounds to me like yet another example of the consequences of moving from the reverse FQDN to the 'harbour-*' prefix. I have ranted about this decision before; it really seemed like a rushed "let's ship this" decision which ends up biting you in your behind on so many unforeseen areas. People are talking about banning apps with 'harbour-*' prefix, and the original issue that it's a "first to the mill" approach. -- Med venlig hilsen / Best Regards Thomas Tanghus _______________________________________________ SailfishOS.org Devel mailing list
