@Paul-Colby if you have any insights, can you please help me with this

@inkfil At Qt6 all(?) enumerated types have been moved from from a "general, high-level" class/namespace --- like Qt::AlignLeft or QVideoFrame::WriteOnly --- down into a more "specific, low-level" class/namespace --- like Qt::AlignmentFlag::AlignLeft or QVideoFrame::MapMode::WriteOnly. You need to change all your code accordingly. There isn't a definitive list, you just have to find out and do it as necessary. In https://stackoverflow.com/questions/72086632/migrating-to-qt6-pyqt6-what-are-all-the-deprecated-short-form-names-in-qt5 and/or https://pypi.org/project/PyQtEnumConverter/ somebody wrote some kind of converter for Python/PyQt6 for this, maybe it will give you inspiration to understand what has changed.

@Dmitriano It is probably not a trivial question because, as far as I see, setting window width and height to Screen.width and Screen.height is not a solution, because there can be task bar and something else (I do not know what can it be on iOS) that partially occupies the screen.

Great ! Thank you very much.

It does not work with qmake and I would rather search the bug in the lib you link against.

@SGaist Hey so the reference problem is solved. Seems like the file can be opened, the player works but there is no sound :-/. I'll probably open another thread for this issue. Thanks for the help again! EDIT: Or maybe it's working :D. On other devices I got a report that the sound is OK. Will investigate that further!

you can use CrossQFile. CrossQFile is a QFile that supports android uri. https://github.com/mahdize/CrossQFile

@vudangkhoa2906 said in Image orientation with qml Camera: Screen.orientationUpdateMask I never specified an orientation update mask, and this readonly property bool isPortrait: (Screen.primaryOrientation === Qt.PortraitOrientation || Screen.primaryOrientation === Qt.InvertedPortraitOrientation) works fine for me, maybe you don't need it ? 🤷‍♂️

Hi, You should contact the folks from LastPass to check how applications can integrate/communicate with their application.

Then study the gstreamer implementation for example and start from there. The pattern is to have a "session class" that does the work and then provide all the interfaces you support that will be using said session class.

@raven-worx mmh, I'm unsure but I'll look into it. However that gave me an idea. The TextInput QML-Item should have it's own c++ class(I'm however unsure what it's called), somewhere with QQuickItem as it's very base class. I could look into creating my own myTextInput Item that handles the QInputMethod-Query

Ok, the problem solved itself with update to Qt 5.11.2 (while running iOS12). Thanks for reading.

Thank you very much.

@ekkescorner Oh, OK, thanks. I thought we could put this in the build settings: QMAKE_TARGET_BUNDLE_PREFIX = org.ekkescorner QMAKE_BUNDLE = c2g.qtws

@VRonin yes - it's a list of QObject* each entry describes a File: Folder, File Type (Image, Video, PDF, ...) Path Name (obsolet for iOS Photos) entries (if Folder) ... and I'm constructing the collection per ex. from PHFetchResult *smartAlbums = [PHAssetCollection fetchAssetCollectionsWithType:PHAssetCollectionTypeSmartAlbum subtype:PHAssetCollectionSubtypeAlbumRegular options:nil];

@aha_1980 Thank you for exact answer. I am able to call the script with help of Qt creator Project settings.

the code above only fetches smart albums. if you also need albums created manually from user, you must fetch them, too: PHFetchResult *userCollections = [PHCollectionList fetchTopLevelUserCollectionsWithOptions:nil]; and if you need sync’d albums: PHFetchResult *syncedAlbums = [PHAssetCollection fetchAssetCollectionsWithType:PHAssetCollectionTypeAlbum subtype:PHAssetCollectionSubtypeAlbumSyncedAlbum options:nil]; user collections tested, sync’d collections not tested yet because I don’t need them

Hi, Thanks !

Hi @tansgumus , Apple is very conservative in allowing developers long term background threats/events. Taken from the Apple docu: Implementing Long-Running Background Tasks For tasks that require more execution time to implement, you must request specific permissions to run them in the background without their being suspended. In iOS, only specific app types are allowed to run in the background: Apps that play audible content to the user while in the background, such as a music player app Apps that keep users informed of their location at all times, such as a navigation app Apps that support Voice over Internet Protocol (VoIP) Newsstand apps that need to download and process new content Apps that receive regular update from external accessories Apps that implement these services must declare the services they support and use system frameworks to implement the relevant aspects of those services. Declaring the services lets the system know which services you use, but in some cases it is the system frameworks that actually prevent your application from being suspended. That said, a navigation app should fall in this category. But as it is, you're bound to do it in OBjective-C but its relative easy to include ObjectiveC code in Qt.

AFAIK, no. But you can check that yourself.

here's the Blog: http://blog.qt.io/blog/2017/12/01/sharing-files-android-ios-qt-app/ thx to all helping me with this

A quick update on this. Someone got asigned to it, and theres a workaround, in the in the broader sense of the word. There's the Qt::WindowStates flag Qt::MaximizeUsingFullscreenGeometryHint that you can set: //QWidgets: { //e.g. Constructor setWindowFlag(Qt::MaximizeUsingFullscreenGeometryHint, true); } //QML: import QtQuick.Window 2.1 // Import needs to be higher than 2.0 Window{ flags: Qt.MaximizeUsingFullscreenGeometryHint id: window ..... } now the App fills the whole screen in Portrait-and Landscapemode. Tor Arne Vestbø, to whom the ticket was asigned to, says an automatic content margin is in the making, but untill than one has to adjust the UI oneself. Tor Arne Vestbø said in QTBUG-64574: If you set the Qt::MaximizeUsingFullscreenGeometryHint window flag, the window will also cover the area under the statusbar, etc. But we don't have any APIs to automatically add margins for the inner content, the stuff you don't want under the statusbar, so for now you have to do that manually. I'm working on the latter as we speak. I had no idea, that that window flag existed, or was not aktivated by default - on mobile apps. I can work with that. The ticket is still open but my problems are solved. I'll close this topic.

@QtDeveloping94 said in Access to IOS Camera Roll, implement .plist failes: NSPhotoLibraryUsageDescription That was it, thanks!

Did you completely read the iOS note of the function and the linked articles ?

Hi @eLim I am also facing the same issue in my Qt iOS application. Could you please help me to understand what part of javascript, iOS is restricting as I am using Angular to develop the web application. Could you please provide more information what you did to resolve this issue. Thanks in advance.

@GTDev Thanks for the reply. I will go on with V-Play and try to implement my app with V-Play for now. But if anybody has another idea why this happens I would be grateful for cheering.

@farshad-bayat I think you have the same Problem as described here https://bugreports.qt.io/browse/QTBUG-59097