04-22-2012 10:46 AM
I started getting support emails last night. I just updated my pb OS and sure enough all of my Qt apps close instantly after the splash screen closes.
Is anyone else having this issue(s)?
I am just heading out the door on my way to the airport for a 3 day buisness trip (what timing), will have to fire up the debugger later to see what's happening...
Thought I would post here first and see if anyone else has figured out what's happening...
RIM, any chance we can get a warning for the update untill this gets sorted?
Jon
04-22-2012 07:41 PM
Nothing has changed in any of my Qt apps. You were probably using something in your apps that did change (an API or something in descriptor file maybe?).
You will know soon enough when you check out your logs/log file though.
04-23-2012 08:54 AM
04-23-2012 03:24 PM
I have no problems with my Qt-Apps after update. I also use some other native functions from NDK.
04-23-2012 03:43 PM - edited 04-23-2012 03:51 PM
OK, thanks for the input guys.
These are pretty straightforward Qt apps that dont use any odd API's or anything so not sure what could be the problem. I pulled them all from the store until I can figure out what's happening, likely not till I get home tomorrow night.
2 are Qt widget based apps and 4 are qml apps that use the symbian qml components that I ported over to QNX.
The problem is that I packaged these before the Qt bb SDk was released that supported debugging on device(I used the old git hub Qt port for these apps). I will have to change the pro and xml files now so I can deploy from the SDK and use the debugger to see what's happening...
Here is what my pro and descriptor look like for one of the qml apps, maybe somthing will stand out to those in the know?
Cheers,
Jon
# Add more folders to ship with the application, here
folder_01.source = qml/ECalc_USA
folder_01.target = qml
DEPLOYMENTFOLDERS = folder_01
# Additional import path used to resolve QML modules in Creator's code model
QML_IMPORT_PATH =
TARGET = E-CalcUSA
QMAKE_LFLAGS += '-Wl,-rpath,\'./app/native/lib\' '
package.target = $${TARGET}.bar
package.depends = $$TARGET
package.commands = blackberry-nativepackager \
-package $${TARGET}.bar -arg -platform -arg blackberry \
-arg -platformpluginpath -arg ./app/native/lib/platforms \
blackberry-tablet.xml $$TARGET \
-e qml qml \
-e icon.png res/icon.png \
-e ssLandscape.png res/ssLandscape.png \
-e ssPortrait.png res/ssPortrait.png \
-e $$[QT_INSTALL_LIBS]/libQtCore.so.4 lib/libQtCore.so.4 \
-e $$[QT_INSTALL_LIBS]/libQtGui.so.4 lib/libQtGui.so.4 \
-e $$[QT_INSTALL_LIBS]/libQtOpenGL.so.4 lib/libQtOpenGL.so.4 \
-e $$[QT_INSTALL_LIBS]/libQtNetwork.so.4 lib/libQtNetwork.so.4 \
-e $$[QT_INSTALL_LIBS]/libQtDeclarative.so.4 lib/libQtDeclarative.so.4 \
-e $$[QT_INSTALL_LIBS]/libQtSql.so.4 lib/libQtSql.so.4 \
-e $$[QT_INSTALL_LIBS]/libQtSvg.so.4 lib/libQtSvg.so.4 \
-e $$[QT_INSTALL_LIBS]/libQtScript.so.4 lib/libQtScript.so.4 \
-e $$[QT_INSTALL_LIBS]/libQtXmlPatterns.so.4 lib/libQtXmlPatterns.so.4 \
-e $$[QT_INSTALL_PLUGINS]/platforms/libblackberry.so lib/platforms/libblackberry.so
QMAKE_EXTRA_TARGETS += package
# The .cpp file which was generated for your project. Feel free to hack it.
SOURCES += main.cpp
HEADERS += settings.h
# Please do not modify the following two lines. Required for deployment.
include(qmlapplicationviewer/qmlapplicationviewer. pri)
qtcAddDeployment()
OTHER_FILES += \
blackberry-tablet.xml
<?xml version="1.0" encoding="utf-8" standalone="no"?> <qnx xmlns="http://www.qnx.com/schemas/application/1.0"> <id>com.snappyappz.ecu_pb</id> <filename>E-CalcUSA</filename> <name>E_Calc USA</name> <versionNumber>1.0.0</versionNumber> <buildId>10</buildId> <description>Common electrical calculations in a snap!</description> <copyright>2012</copyright> <initialWindow> <systemChrome>none</systemChrome> <transparent>false</transparent> <autoOrients>true</autoOrients> <aspectRatio>portrait</aspectRatio> </initialWindow> <publisher>SnappyAppz.com</publisher> <permission system="true">run_native</permission> <category>core.games</category> <icon><image>res/icon.png</image></icon> <splashscreen>res/ssLandscape.png:res/ssPortrait.png</splashscreen> <!--<env var="QT_DEBUG_PLUGINS" value="1"/> --> <env var="LD_LIBRARY_PATH" value="app/native/lib"/> <env var="QT_QPA_FONTDIR" value="/usr/fonts/font_repository/liberation"/> <env var="QT_QPA_PLATFORM_PLUGIN_PATH" value="app/lib/platforms"/> <env var="QML_IMPORT_PATH" value="app/native/qml/imports"/> <env var="QT_PLUGIN_PATH" value="app/native/lib"/> </qnx>
04-23-2012 03:47 PM - edited 04-23-2012 03:49 PM
Are the Qt apps you guys have using the old git hub port too?
I am currently making a proper pdf reader for the playbook and the OS update seemed to make no difference with that app in its current state. However I am using the latest Qt4.8.1 source from git along with the new bb Qt SDK... Just thinking out loud here...
Cheers,
Jon
04-23-2012 04:02 PM
I tested using the PlayBook port of Qt Creator and my app launched without error:
https://github.com/blackberry/Qt/downloads
Let us know once you get a chance to do some testing if you need help digging into it!
04-23-2012 04:16 PM
OK, thanks!
This may be a stupid question, please bear with me...
Is there a way to deploy just the bar file (the one I submitted to the store) with the Qt bb port Garett linked to above and get debugging output with the included Qt creator? This would save me some time and likely give an accurate indication of what's going on with those packages...
Cheers,
Jon
04-23-2012 05:17 PM - edited 04-23-2012 05:18 PM
Hmmm....
I can't reproduce the problem, they work fine when deploying with the latest 4.8.1 libs and theQt creator linked to above... Its just the packages on the store done with the old port that dont work anymore.
I guess I will just repackage them with the latest 4.8.1 and update them all...
If any of you RIM developers have any hints as to what broke here I would be interested in what happened, some kind of binary break I suppose?
I will gladly supply the offending bar packages if anyone is interested.
Cheers,
Jon
04-23-2012 07:42 PM - edited 04-23-2012 07:44 PM
Can you grab logs/log first from the failing package first?
Just use a debug token on your app and use blackberry-deploy to -getfile.
It could be something very simple (most likely since it works for everyone else).