Meta tags:
description= Qt (Android, iOS, W10);
Headings (most frequently used words):
qt, android, work, app, for, back, overview, next, article, home, topics, creator, patch, apps, to, device, run, google, play, and, managed, deploy, the, update, test, conference, mostly, harmless, popup, install, activate, external, store, blackberry, uem, secure, qml, first, with, some, of, ripple, key, text, selection, handles, preferences, quick, controls, at, stores, world, summit, debug, qtcreator, devices, qtbug, 59293, 59026, eclipsecon, europe, 2016, user, private, your, in, release, build, ios, not, is, bug, business, tool, publish, developer, policies, client, statusbar, connection, boot, enterprise, 12, development, stages, dev, production, imports, demo, buttons, remain, color, effect, problems, start, settingspath, working, directory, tools, verify, installation, gallery, clone, my, examples, from, github, soon, available, screenshots, vs, as, two, multi, package, names, manifest, develop, workflow, material, force, background, when, hidden, very, signing, issue, import, could, be, resolved, qqmlcomponent, component, ready, binding, loops, please, kit, or, choose, mkspec, qmake, headerpad_max_install_names, ignored, member, multiple, groups, supporting, files, resources, issues, bitcode, prf, adding, openssl, without, closepolicy, quits, modal, doesn, block, patches, bugs, progress, community, wiki, forum, lists, intro,
Text of the page (most frequently used words):
the (210), and (147), for (125), app (108), work (91), you (83), android (80), your (77), this (74), from (74), apps (52), can (40), with (35), #creator (34), mobile (33), will (33), #device (33), new (32), ios (32), google (32), some (31), using (31), are (31), here (30), also (28), play (26), blackberry (26), qml (25), see (25), controls (24), run (23), there (23), but (23), user (23), build (22), use (22), have (21), now (21), like (21), print (21), store (20), not (20), install (20), one (20), test (20), devices (20), more (19), open (18), patch (18), all (18), update (18), managed (18), bitcode (18), release (17), back (17), qtbug (17), that (16), first (16), next (16), only (15), start (15), 2017 (15), import (15), development (14), conference (14), working (14), overview (14), get (14), qtquick (14), bin (14), private (14), blog (13), make (13), different (13), git (13), fembed (13), about (12), bug (12), installed (12), then (12), add (12), qtquickcontrols2 (12), must (12), popup (12), org (12), customer (12), admin (12), uem (12), comment (11), loading (11), share (11), tweet (11), github (11), always (11), time (11), where (11), deploy (11), already (10), opens (10), window (10), tumblr (10), 2016 (10), drawer (10), please (10), running (10), project (10), should (10), tools (10), file (10), same (10), was (10), got (10), openssl (10), warning (10), data (10), business (9), https (9), want (9), take (9), article (9), projects (9), external (9), doesn (9), doing (9), qtcreator (9), beta (9), path (9), issues (9), key (9), xcode (9), com (8), account (8), demo (8), material (8), source (8), home (8), topics (8), navigation (8), create (8), files (8), case (8), need (8), without (8), something (8), version (8), leave (8), again (8), kit (8), fixed (8), example (8), could (8), secure (8), marker (8), debug (8), activate (8), package (8), adb (8), name (7), dev (7), develop (7), quick (7), good (7), 59293 (7), jpnurmi (7), select (7), linguist (7), into (7), tool (7), don (7), any (7), daten (7), sdk_580 (7), repo (7), hint (7), problems (7), builds (7), developer (7), added (7), march (7), screenshots (6), know (6), used (6), code (6), 59026 (6), out (6), gallery (6), osx (6), way (6), step (6), found (6), default (6), these (6), _qt_sdks (6), read (6), qmake (6), terminal (6), easy (6), component (6), while (6), ekkescorner (6), users (6), list (6), color (6), ignore (6), qtcreatorbug (6), output (6), enterprise (6), security (6), email (5), log (5), xxx (5), world (5), eclipsecon (5), europe (5), howto (5), available (5), easier (5), able (5), yet (5), download (5), look (5), ripple (5), try (5), idea (5), similar (5), environment (5), which (5), text (5), qtproject (5), commercial (5), type (5), android_armv7 (5), info (5), unfortunately (5), pages (5), error (5), mostly (5), harmless (5), true (5), workaround (5), built (5), well (5), buttons (5), building (5), warnings (5), groups (5), happens (5), imports (5), qtgraphicaleffects (5), resolved (5), profile (5), has (5), address (5), policies (5), required (4), comments (4), bar (4), content (4), wordpress (4), newer (4), ekke (4), windows (4), amazon (4), greater (4), apple (4), summit (4), probably (4), finished (4), bottom (4), tabbar (4), page (4), clone (4), what (4), fortunately (4), effect (4), attention (4), most (4), much (4), verify (4), clang_64 (4), preferences (4), cannot (4), find (4), developing (4), support (4), ndk (4), set (4), script (4), settingspath (4), old (4), installer (4), components (4), small (4), before (4), installing (4), application (4), each (4), prepare (4), radiobutton (4), nurmi (4), cherry (4), pick (4), cloned (4), branch (4), failed (4), features (4), appwindow (4), modalpopupactive (4), keys (4), two (4), fails (4), behind (4), remains (4), wrong (4), issue (4), prf (4), releases (4), ignored (4), codereview (4), reference (4), binding (4), errors (4), module (4), paths (4), works (4), signing (4), logs (4), extra (4), inside (4), updates (4), workflow (4), accounts (4), activated (4), request (4), emm (4), connection (4), shell (4), pegelmeter (4), manage (3), report (3), conferences (3), conference2go (3), session (3), detail (3), iphone (3), hopefully (3), runs (3), others (3), upload (3), visible (3), soon (3), series (3), examples (3), patches (3), critical (3), configure (3), search (3), right (3), correct (3), installation (3), access (3), translations (3), changed (3), configuring (3), because (3), r10e (3), directory (3), multiple (3), folder (3), settings (3), macos (3), infos (3), sure (3), commit (3), down (3), changes (3), show (3), selection (3), handles (3), updating (3), property (3), onbackpressed (3), modal (3), closepolicy (3), behavior (3), popups (3), crash (3), many (3), opened (3), they (3), adding (3), toolbutton (3), favmenubugfix (3), opening (3), later (3), left (3), complex (3), flags (3), googleplay (3), pane (3), group (3), confirmation (3), when (3), yes (3), choose (3), mkspec (3), listview (3), impl (3), provisioning (3), very (3), published (3), testing (3), ways (3), testers (3), stage (3), pro (3), customers (3), production (3), publish (3), stages (3), firewall (3), samsung (3), delete (3), usual (3), client (3), sign (2), subscribed (2), subscribe (2), other (2), former (2), bb10 (2), services (2), older (2), speakers (2), schedule (2), sourcecode (2), c2gqtws_x (2), fire (2), blackberry10 (2), ipads (2), phones (2), tablets (2), stores (2), october (2), last (2), years (2), developed (2), year (2), did (2), generated (2), dsl (2), cascades (2), mode (2), native (2), faster (2), approved (2), moment (2), apk (2), hours (2), community (2), forum (2), lists (2), follow (2), swipeview (2), stackview (2), moving (2), help (2), even (2), check (2), thx (2), best (2), configured (2), configuration (2), under (2), exist (2), lupdate (2), lrelease (2), looking (2), strings (2), marked (2), translate (2), compiles (2), english (2), language (2), rename (2), sources (2), comfortable (2), important (2), sdk (2), directories (2), theme (2), changing (2), restart (2), execute (2), named (2), besides (2), contents (2), parameter (2), click (2), notice (2), online (2), downloads (2), steps (2), startups (2), post (2), license (2), developers (2), maintenance (2), february (2), thanks (2), helping (2), radiobuttons (2), export (2), android_ndk_root (2), your_path_to (2), repo_android (2), e91c9feab8a0cf4cff71cc68ab0f001b1531504f (2), stopper (2), fix (2), focus (2), tested (2), thing (2), dialogs (2), 59670 (2), false (2), event (2), accepted (2), yourself (2), goes (2), thru (2), block (2), closeonescape (2), policy (2), per (2), closeonpressoutside (2), multi (2), qnetworkaccessmanager (2), updated (2), libraries (2), include (2), own (2), finally (2), long (2), didn (2), argument (2), documentation (2), http (2), seen (2), between (2), worked (2), loader (2), favmenucomponent1 (2), favmenucomponent2 (2), drawerfavoritesmenubutton (2), wasn (2), pressing (2), after (2), fingers (2), released (2), comfort (2), else (2), let (2), enable_bitcode (2), setting (2), qmake_cflags (2), qmake_cxxflags (2), qmake_objective_cflags (2), qmake_lflags (2), replace (2), created (2), testflight (2), qrc (2), member (2), supporting (2), resources (2), membership (2), another (2), may (2), happen (2), headerpad_max_install_names (2), tobias (2), hunger (2), applications (2), usr (2), clang (2), loop (2), detected (2), implicitwidth (2), tab_pages_x (2), reserved (2), loops (2), does (2), contain (2), plugins (2), automatic (2), qqmlcomponent (2), ready (2), nothing (2), panic (2), expected (2), dir (2), them (2), blogged (2), swipe (2), tab (2), compile (2), through (2), specific (2), accessing (2), newest (2), side (2), location (2), fetch (2), refs (2), 187564 (2), fetch_head (2), following (2), once (2), publishes (2), send (2), closed (2), would (2), supports (2), 17863 (2), means (2), three (2), names (2), manifest (2), publishing (2), servers (2), cases (2), server (2), needed (2), typically (2), vpn (2), solution (2), days (2), based (2), together (2), monthly (2), boot (2), hardware (2), those (2), chrome (2), urls (2), statusbar (2), sent (2), mail (2), password (2), domains (2), ask (2), allow (2), profiles (2), guide (2), user_id (2), placed (2), variable (2), qt5 (2), bindings (2), qtactivity (2), lograbbit (2), starts (2), userinfo (2), tips (2), tricks (2), website, write, collapse, subscriptions, view, site, reader, privacy, join, subscribers, floorplan, pixelc, tablet, eclipse, brandnew, style, entities, speaker, track, room, xtext, xtend, started, ago, generate, end, mobadsl, lumia, haven, sorry, enough, loads, smoother, just, prefer, sideloading, ludwigsburg, germany, intro, wiki, appbus, category, appetizers, patchqtbug, bugs, congrats, priv, desktop, cycle, tip, saved, impression, shortcut, executable, commands, translatable, translation, deployed, trick, linguist_de, languages, i18n, trouble, ones, locations, gradle, devcies, flat, german, macbookpro, versions, collision, sthore, save, exec, qtc_settings, editor, instances, having, launching, wait, included, part, pathes, spaces, double, selected, offer, www, plan, licensing, independent, faq, downloading, perhaps, fresh, going, esp, 46a936f, missing, registrations, author, date, mon, feb, 0100, insertions, checkout, scrolling, affected, problem, done, aware, jira, reprted, bugreports, browse, qqmlapplicationengine, load, unavailable, trying, delegates, finding, promised, classified, applicationwindow, width, 410, height, 680, bool, showtoast, qstr, allowed, return, main, noautoclose, onopened, onclosed, blocking, shortcuts, explicitely, closes, chance, catch, quits, esc, reports, requests, had, dopenssl_threads, 39d3d4122a132f1f73f7e7ed079de3f067775dde, providing, prebuilt, libs, myself, origin, marco, piccolino, scripts, job, discussion, tried, 59375, unknown, mandroid, doc, opensslsupport, html, things, crashing, discussions, forums, seeing, differences, todo, firewalls, removed, android7, onclicked, navigationbar, favmenuloader, sourcecomponent, toggling, seems, reset, completely, top, agein, menu, suddenly, noticed, strange, remain, leaving, zone, gone, lessthan, qmake_xcode_version, macx, simulator, driver, conjunction, xarch, note, affects, makefile, generator, passed, care, mkspecs, uikit, annoying, hundreds, jakepetroules, reported, 58754, 59352, unused, during, compilation, far, betatest, filled, 192, logging, 14926, xcodebuild, 5107, 303392, _qt_workspaces, work_580, c2gqtcon_x, images, indicates, malformed, preserved, targets, unaffected, than, compiling, 185929, bitcode_bundle, why, message, bugreport, 17794, toolchains, xcodedefault, xctoolchain, matches, target, better, scenario, preferredhighlightend, libtab_pages_x, null, reporting, wrote, 17819, styles, information, contained, modules, dump, qmlplugindump, returned, exit, arguments, nonrelocatable, parsing, dependencies, outputofqmlimportscanner, illegal, value, proecess, qmlimportscanner, typelist, plugin, loaded, libqtgraphicaleffectsplugin, valid, mach, binary, invalid, magic, 7f454c46, general, messages, day, 47389, universal, simply, caused, scope, 59350, deleting, team, xyz, certificate, ekkehard, gentz, 4a4, vv3, product, moved, 580, matter, longer, listing, devs, happened, repos, qtcon, qobject, delegate, datepicker, stacks, tabs, bars, swiped, stacked, labels, icons, simple, replacing, writing, makes, tests, control, system, went, technical, point, properties, replaced, compare, qnam, repo_ios, force, background, hidden, provides, took, reproducable, amount, sometimes, detect, explain, sends, creates, adds, until, directly, variables, environemts, manually, dynamic, enable, connected, change, highly, recommended, forbid, bluetooth, nfc, camera, url, outside, gmail, against, mockup, manages, via, transparently, provider, cloud, premises, free, formely, known, bes, vmware, airwatch, mobileiron, providers, experiences, management, scenarios, sooner, focused, aka, knox, how, levels, transition, software, licensed, partners, verifies, presented, tcl, congress, barcelona, keyone, nougat, rooted, second, browser, sites, sitting, office, intranet, encrypted, box, transport, current, currently, exists, switch, off, airplane, personal, goofle, activation, automatically, enter, receive, sceenshots, easiest, dedicated, options, non, matching, rights, still, described, bes12, normal, artwork, description, uploaded, registered, progress, 17862, externaltools, kill, platform, clear, start_pegelmeter_work, executes, checked, printed, forgot, tell, above, stop, close, special, gives, filtering, recommend, filter, logcat, libpegelmeter_x, give, starting, loosing, command, process, 1799924875, 141078676, normally, bound, topic, appear, twice, optional, deploying, debugging, goods, receipt, allaboutmyb, 101, ekkes, teatimer, jam, sercar10, servicecars, opendataspace, ekkesexpresscharts, keepass, bbm, meetings, drives, mobility, marketplace, classic, passport, computing, invocation, framework, performance, maps, workshops, ide, introduction, w10,
Text of the page (random words):
k app you can run the app from terminal as work app adb shell am start user 10 n org ekkescorner xxx pegelmeter dev org qtproject qt5 android bindings qtactivity qtcreator starts the app without user which always will use the default one 0 i ll open a bug report and request to add a variable user_id so this can be placed inside pro and added to adb start command by qt build process starting the work app from terminal you re loosing the log output inside qt creator workaround could be to log from adb or to use an extra tool this will give you the logs using adb adb d logcat libpegelmeter_x so d s a special tool gives you some more comfort filtering the logs for osx i can recommend lograbbit it s easy to filter out the logs from your app external tool as we have seen build and run the app starts the private app so you have to stop and close the private app and then start the work app from terminal to make this easier i added this to external tools in qt creator i checked output show in pane but nothing is printed probably i forgot something to tell external tools that app output should be visible in application output pane as long as this doesn t work i m using lograbbit see above external tools start_pegelmeter_work sh executes this script bin sh cd path to platform tools adb shell pm clear user 0 org ekkescorner xxx pegelmeter dev adb shell am start user 10 n org ekkescorner xxx pegelmeter dev org qtproject qt5 android bindings qtactivity now it s easier build and run app externaltools kill running private app and start work app i would like to use a variable for user id and also for app name and app package see qtcreatorbug 17863 and here s the request to add user_id to be placed inside pro qtcreatorbug 17862 back deploy android work app to google play next article work in progress home overview topics tweet share on tumblr print opens in new window print like loading in mobile development qt for mobile qt for work deploy android work app to google play march 15 2017 leave a comment publish to google play store for work your blackberry uem admin must publish your app to google play store for work the app must not be uploaded to google play but will be registered the workflow is similar to publishing a normal app to google play so you need screenshots artwork description here s a guide what the admin has to do this guide is from 2016 but the workflow still is the same all described for bes12 will work using uem 12 6 as soon as google has approved the app the admin can configure on which devices users user groups the app should be installed developer policies the admin typically will create policy profiles matching the rights a user group should have for work apps attention to be able to deploy debug builds from qtcreator to your device the admin must add these extra policies to developers apps allow installation of non google play apps allow developer options if you cannot deploy and run work apps from qtcreator ask your admin if these policies are set for your device back activate android device for work next article debug and run managed qt android app qtcreator home overview topics tweet share on tumblr print opens in new window print like loading in mobile development qt for mobile qt for work activate android device for work march 15 2017 leave a comment there are different ways to activate a device managed accounts google domains my example and sceenshots are based on managed accounts which is the easiest way if you re using google domains then it s much more complex and for each user you need a dedicated work google play account the newest blackberry uem 12 6 supports managed accounts to activate a android device for work managed account you ll receive an email from the admin email address password blackberry uem client please download the blackberry uem client app from google play open the uem client and enter email address and password configure your profile device will be activated play store for work automatically some work apps will be added here you see the play store for work left and the usual private play store please open the play store for work if you don t have used a google mail address different from your personal goofle mail address for activation it can happen that you get an error try to switch off on the airplane mode or restart the device to see your work apps your work apps in this case there s one app available the app you sent to the admin two apps work private install the app as usual and you ll get 2 apps one as private one as work app we only need this app as work app so you can delete the private one now as your app exists as a work app you can deploy updates from qt creator and use the work profile android for work statusbar open your work app and take a look at android statusbar you ll always see if the current app is a work app and you ll also see if currently there s a secure connection to server vpn secure connection all your work apps will use the secure connection there s also a second browser chrome for work opening sites from chrome for work or accessing urls from your work app always goes thru the secure connection this means those urls will be opened behind the firewall same way as if you re sitting in your office using the intranet data used by work apps is encrypted and secure out of the box on transport and also on your device secure boot using blackberry android devices there s some extra security built into the hardware those devices cannot be rooted read more here and here blackberry and android devices you have read that there will be no more devices built by blackberry yes blackberry finished transition from hardware to software blackberry licensed devices to partners but verifies security first new device was presented by tcl at mobile world congress in barcelona keyone with android nougat 7 1 three more new devices will follow blackberry android devices always get the monthly security updates for android per ex security patches from march 2017 it s up to you or your customers how many levels of security they need android for work is the first step using devices with secure boot the next one samsung does something similar with samsung knox and samsung devices but fails with monthly security updates back overview managed android devices next article deploy android work app to google play home overview topics tweet share on tumblr print opens in new window print like loading in mobile development qt for mobile qt for work overview managed android devices march 15 2017 leave a comment if you re developing mobile business apps sooner or later customers will request to debug build and run on managed devices this blog post is focused on google for work android enterprise aka android for work google for work android enterprise there are different ways to run work applications devices may only contain work apps or private and work apps are installed together from my experiences in most cases there are private and work apps together on devices read more about emm enterprise mobile management and different scenarios here there are some emm solution providers blackberry mobileiron vmware airwatch blackberry uem 12 6 my examples are based on blackberry uem 12 6 formely known as bes 12 you can try out uem for 30 days cloud version or 60 days on premises for free using a managed device is like working behind the firewall via vpn but all is transparently managed by the emm solution provider emm admin manages users user groups devices policies and apps here you can download the policies for blackberry uem get an overview of blackberry uem here development stages dev test production developing a new app there are typically 3 stages develop ui with mockup data no access to servers needed test against test environment release for production environment stage 1 i m using googleplay closed beta test to deploy the apps to beta testers from customer adding testers only gmail address is needed for stages 2 and 3 your device must be activated as android for work device or you should request a device to test on from your customer this is the only way to get access to data servers behind the firewall in most cases there will be no url you can use from outside one device can only be activated as work device for one server blackberry uem it s highly recommended to test your app as work app the admin can forbid features bluetooth nfc camera to manage apps your customer has to use a google developer account to be able to publish apps through google play for work multi android package names in manifest attention you must change the android package name to enable your customer publishing the app to google play for work because the package name from stage 1 is already connected to your own google developer account from beta testing also your enterprise customers can have different environemts for dev test production with different google developer accounts to get a specific play store for work for each environment this means you must build releases for up to three or more different package names changing the package name manually in android manifest is not so comfortable you can have a dynamic way following this blog article best would be qt creator supports this directly using variables in pro see qtcreatorbug 17863 develop test release workflow for work apps here s an example workflow add your app to google play closed beta test android package name my example beta deploy updates to beta testers until stage 1 finished build release android package name my example test and send apk to your customer your customer publishes app to googleplay for work your customer creates user and profile for you and adds the app to your user or user group your customer sends an email to activate a device you activate your device and install the app from google play for work on your device now you can develop build and run your app from qt creator build update releases and send to your customer your customer publishes update to google play for work so others can test your update hint you can only build and run your app as work app if customer has published your app once to google play for work and you installed it once following pages will explain the steps in more detail activate android device for work deploy android work app to google play debug and run managed qt android app qtcreator back eclipsecon europe next article activate android device for work home overview topics tweet share on tumblr print opens in new window print like loading in mobile development qt for mobile qt for work patch qt 5 8 0 for qtbug 59293 march 6 2017 leave a comment you should already have installed the patch for qtbug 59026 radiobuttons type if you re developing android apps while updating my projects from qt 5 7 to 5 8 i was running into another show stopper bug using the drawer or bottom navigation bar some color from pressing the buttons down remains after fingers are released this happens on android and ios and the amount of color is different from case to case sometimes not easy to detect here are some screenshots so you can verify if this happens also in your apps running example apps like qtquickcontrols2 gallery all works well it took me some time to have a small reproducable test case and i opened qtbug 59293 again jpnurmi could help and provides a patch material force ripple background when hidden now it s easy to patch hint this time we must do this for the android kit and also for the ios kit open a terminal and do this to patch your android kit attention i m using the android repo i already cloned for the first patch export android_ndk_root your_path_to android ndk r10e cd your path to store cloned repo_android cd qtquickcontrols2 git fetch https codereview qt project org qt qtquickcontrols2 refs changes 64 187564 1 git cherry pick fetch_head your path where qt is installed 5 8 android_armv7 bin qmake make make install now we re doing the same for ios create a folder where you want to store the repo then cd your path to store cloned repo_ios git clone branch 5 8 git code qt io qt qtquickcontrols2 git cd qtquickcontrols2 git fetch https codereview qt project org qt qtquickcontrols2 refs changes 64 187564 1 git cherry pick fetch_head your path where qt is installed 5 8 ios bin qmake make make install hint make can take some time there are some other ways you only have one repo for android and ios see comments from jpnurmi at qtbug 59293 now the ripple effect is working again inside a drawer with qt 5 8 and qtquickcontrols2 one use case is left where some color remains but there s a workaround so i can go on moving my projects from 5 7 to 5 8 thanks jpnurmi helping me to make this work back patch qt 5 8 bug 59026 next article update 5 7 5 8 mostly harmless home overview topics tweet share on tumblr print opens in new window print like loading in install qt mobile development qt for mobile mostly harmless update qt 5 7 0 qt 5 8 0 march 4 2017 leave a comment update 2017 03 24 added info about problems with popups and android back key update 2017 03 13 updated my openssl repo to fix crash with qnam update 2017 03 09 added info adding openssl added reference to comment from tobias hunger on choose a mkspec update 2017 03 07 added a very first ios build signing issues and b ios build issues patch bitcode prf update 2017 03 06 critical qtbug 59293 fixed see patch i m not using the maintenance tool i m always installing a new qt release at a different location and also start qt creator with settingspath as blogged here then it s easier to work with old and new release side by side and compare update qml imports from a technical point you can use the old imports i m always doing search replace to update the imports then i m sure all my qml files are accessing the newest controls and properties updating from 5 7 to 5 8 i replaced import qtquick 2 6 import qtquick controls 2 0 import qtquick controls material 2 0 with import qtquick 2 7 import qtquick controls 2 1 import qtquick controls material 2 1 using a source control system like git it s a good idea to do this in an extra branch then it s easier to go back if something went wrong first test with demo and conference apps while writing this blog series on qt for mobile i developed some demo apps where each demo app has a specific focus this makes it easy to do the tests step by step i m replacing the imports then compile and run the app on android and ios devices and take a look at compile and application output and issues and go through the apps to see if all works as before my demo apps simple one page app labels buttons icons stacked pages app stackview swiped pages app swipeview tab bar app tab bars bottom navigation app tool buttons drawer navigation app drawer stacks swipe tabs pages business data app qobject data listview swipe delegate datepicker as next i m testing my conference apps these apps are something more complex and i also test building release and uploa...
|
