In that case, you should take a look at the plugins in QtMultimedia's sources, you have several implementations that you can take inspiration from thus integrating directly in the pipeline rather that having a custom item.

@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 after some discussions with Andy Shaw https://bugreports.qt.io/browse/QTBUG-70072
here's the recommended way to get the correct bundle identifier:

QMAKE_TARGET_BUNDLE_PREFIX = org.ekkescorner QMAKE_BUNDLE = c2g.qtws

this will create the bundle identifier org.ekkescorner.c2g.qtws
no workaround needed anymore

@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 ?

@jsulm We determined that the issue was javascript-related. The page was using javascript to perform the redirect, and iOS didn't like that.

Thanks for the help, though!

@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

@ekkescorner @jpnurmi reminds me that there's a problem if you're using multi-line Text inside Flickable.
just tested.
He's right: as long as the TextArea has focus if you try to scroll the selection will be changed instead of scrolling the page.
If you're outside the field scrolling works well

I'll create a bugreport on this soon.
my workaround: I'm placing a small button (w icon) besides the field to toggle word-selection-mode. just tested. this works.

In most cases my TextFields are single line text where selection works well so I can live with this.

@SGaist thx - have thought the same.
would work well if Active and bad coverage or coming back from suspended when multi signals are received

@SGaist One way to see console output could be to open the system log. Tried, but I can't find it there either. Any hints?
Any way to simulate iPad 2 instead of iPhone 6S?

Build Qt qml plugin for iOS (static plugin)

Plugin Pro file like flow:
TEMPLATE = lib
TARGET = iostestqmlplugin
QT += qml quick
CONFIG += qt plugin c++11 static
uri = IosQmlPluginTest # module name
QMAKE_MOC_OPTIONS += -Muri=$$uri # static plugin must use this

2.qmldir file
module IosQmlPluginTest
plugin iostestqmlplugin
typeinfo plugins.qmltypes #static plugin required
classname IosqmlpluginPlugin # static plugin must set classname for plugin c++ class

TimeLabel 1.0 qrc:/TimeLabel.qml # your self qml document

3.qrc file must contains qmldir file, Qt default put qmldir in qrc file with prefix likes: “/qt-project.org/imports/your-plugin-modele-name”, You can special yourself prefix but must endwiths “your-plugin-module-name” and in main cpp need add addImportPath(eg: engine.addImportPath(“qrc:/your-self-prefix-not-contains-your-plugin-module-name”))

4.put plugins.qmltypes, qmldir and plugin library files together into where Qt install dir’s sub fold name qml($$[QT_INSTALL_QML] Qt default serach path), maybe you can special yourself path in your app pro file by variable QMLPATHS(QMLPATHS += /your/plugin/path)

Init the plugin resources(contains qmldir) at plugin c++ class construction function like:Q_INIT_RESOURCE(your-qrc-file-name);

6.pulugins.qmltypes file it’s required. can gernerate by qmlplugindup tool.

7.refrence QtWebView plugin project from Qt source

usually error:
1.static plugin for module “QtQuick” with name “your-module-name” has no metadata URI
fix by add in pro file:QMAKE_MOC_OPTIONS += -Muri=$$URI #URI = your-module-name
thanks from:https://github.com/wang-bin/QtAV/issues/368

2.Plugin “your-module-name” is missing a classname entry
fix by add in qmldir file: classname your-plugin—c++-name
Reference http://doc.qt.io/qt-5.6/qtqml-modules-qmldir.html

module “your-plugin-module-name” is not installed
fix by: Qmldir file must in plugin qrc file, plugins.qmltypes need in the plugin dir and special in qmldir

@tomaslov
Hello
Did you solve this problem of Barcode scanning on IOS?
If Yes, could you please share the solution?

@VRonin said in Encrypt String (RSA x509) Android, iOS:

@ekkescorner I only now read your username. Sorry for treating you as "not an expert" in network and/or password encryption.

I think you still have 2 options apart from OpenSSL:

Use Android's built in encryption with QAndroidJniObject: https://www.example-code.com/android/rsa_encryptstrings.asp use CryptoC++ https://www.cryptopp.com/wiki/RSA_Cryptography

thx for this worthful info - will try CryptoC++ - need solution for Android and iOS

Hi,

I may be wrong but AFAIK, Apple changed recently its policy about dynamic library in application bundle. Thus its likely related to that.

You should bring this question to the interest mailing list, you'll find there Qt's developers/maintainers. This forum is more user oriented.

@SGaist Thank you very much!

I haven't got around to test it properly yet - but I'm marking this as solved.

Hi Larpon,
we didn't use the Firebase C++ SDK as it is still limited compared to what the native iOS & Android SDKs offer.
You can use our AdMob plugin for iOS & Android for free, here's the documentation how to add it to your Qt project and how to use it:
https://v-play.net/doc/plugin-admob/

Today we released a new update for the plugin so it now also supports rewarded video ads and native ads from AdMob. If you're interested, here is the announcement:
https://v-play.net/updates/release-2-13-0-free-rewarded-videos-native-ads-for-google-admob-qt

Cheers, Chris

@VRonin

Thank you for the suggestion.

The Windows 10 behavior (meaning display issues) it's the same on MacOSX. On Windows 10 I'm building with MSVC2015_64bit. On MacOSX with clang 64 bit.

However, the sound playback issues in iOS devices are far more annoying for me at this point.

We found a way around the problem. Turns out we can use a variation of @kshegunov 's approach and judicious use of error codes returned from Qt.

Pretty complex setup to handle. Indeed, that's likely the best solution at this time.

Happy to hear it. I'm lacking a device with a rotatable screen at the moment, so that recipe involved a little faith.

I solved my problem. I had to manually set the visibility property:

visibility: Window.Windowed