A lot of warnings when adding Content Hub simple example
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
content-hub (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I just added with Ubuntu Content 1.1 a simple example, here is the commit: https:/
Switching that one, I'm starting to get a lot of warnings in my application related to contenthub. This is all at instantation, so before starting any transfer. The default experience shouldn't give any warning:
1. qml: WARNING: Header is an internal component of Ubuntu.Components andits API may change or be removed at any moment.Please use MainView and Page instead.
2. the activeTransfer is null by default, so the Connections will fail in: file:///<…>: Unable to assign [undefined] to QObject*
Maybe we should set a default value to activeTransfer? Or any other idea?
3. file://
I guess that's because something isn't instantiated.
4. Once the peer in peerpicker is chosen, then transferHint triggers some warnigns:
file://
file://
(this is using Components 1.2)
5. hfile:/
description: | updated |
no longer affects: | content-hub (Ubuntu) |
affects: | content-hub → content-hub (Ubuntu) |
The warnings mentioned in numbers 4 and 5 are all internal to the SDK. If we update to 1.3 of the SDK those will go away, but we aren't ready to do that yet. Apps shouldn't have mixed imports for the SDK components, we'll need to provide a version of our components that import 1.3 from the SDK for apps that use 1.3.