I have a a few Flex Builder 3 projects (SDK 3.2/3.5) that I imported into Flash Builder 4. They run fine in debug mode (IE, Firefox, Chrome), with all the swf's and swc's appearing in the bin-debug folder. But, when I try to do an Export Release Build on the main project, I get the following error:
"One or more errors were found while trying to
build the release version. Unable to export."
There is no in errors in the Problems tab, and nothing appears in Console. Just have to hit ok and quit the process.
UPDATE: #doc_80 - I checked the log file, error caused by:
Caused by: java.lang.NoClassDefFoundError: flex2/tools/
oem/OEMException$CircularLibraryDependencyException
Will look into the .project file as suggested by #doc_80
Has anyone else seen this, or know of a fix? I looked a the adobe forum, but their solution to change linked resourses didnt help at all.
Brian
I had the same issue but the reason was desktop.ini file (Windows 7). It appeared in the sme directory with the sound files.
And in the log:
Caused by: java.io.FileNotFoundException: C:.....\assets\ui\sounds\desktop.ini (Access is denied)
... sure this file is hidden. I've delete it manually and everything became OK!
Thanks to the posts here that helped to solve this problem.
Spent all day on this problem, found an answer.
It occurs if your using RSL's in any of your open projects. In my case one of the projects used by the main app was a Library project. Flex 3 SDK is missing files needed for FB4 to handle the RSL dependencies when Export Release build is invoked.
These missing files can be copied from the flex-compiler-oem.jar file in Flex 4 SDK to the same jar in the Flex 3 SDK.
I have put a step by step instructions on my blog:
http://bishoponvsto.wordpress.com/2011/01/19/flash-builder-4-flex-3-sdk-export-release-build-error/
Related
This has been killing me for the last couple of days. I have read everything I can find on this error and have done what xamarin says but it still doesn't work.
I can't get my builds to get through azure pipeline xamarin.ios build and deploy to apple.
When I build locally I get messages like
MTOUCH : warning MT1502: One or more reference(s) to type 'UIKit.UIWebView' already exists inside 'Xamarin.Forms.Platform.iOS, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null' before linking
with a companion message that says no references after linking
when I use --warn-on-type-ref=UIKit.UIWebView with the optimize arg.
When I build on azure in my pipeline, I only see the MT1502 but nothing saying anything after linking. The build gets submitted to Apple and fails because of the ITMS message.
I don't know what to do. I am using the latest macOS vm image, mono 6.8.0.123, xamarin.ios 13.16.0.13, xcode 11.4.1. The pipeline worked fine before April 30 deadline, now no matter what, I can't get the linker to strip UIWebView.
Let me know what other info would be helpful. I am completely stuck at this point.
Thanks.
I just got my build to pass Apple's inspection.
What ended up working for me was building locally and packaging the ipa file. On my mac I then changed the ipa extension to zip and unzipped it. I used terminal to go to the YOURAPPNAME.app "folder" and used grep -r UIWebView . to search for references. Don't forget the . so it searches the current directory. I missed that at first and got some message that grep was listening on stdin.
For me that resulted in a line like this:
Binary file ./Frameworks/PersonalizedAdConsent.framework/PersonalizedAdConsent matches
Now, the important thing to note is the linker never warned about this, so I was completely unaware of it. In my case it was part of Firebase/Admob. I was only one release behind and updating to the latest fixed my problem.
I still am using --optimize=force-rejected-types-removal --warn-on-type-ref=UIKit.UIWebView -warnaserror:1503 as my mtouch args. But builds now get through.
I hope this helps point you guys in the right direction, I've spent the last 3 days just trying to get builds to upload reading every post I could find on the web on this problem.
Solved !! I had to update the way how nugets are included to the iOS project .csproj file. The problem was that linker despite the --optimize=force-rejected-types-removal flag was not removing the UIWebView component form Xamarin.Forms 4.6 probably because it did not see it.
My project was created over two years ago and I was still using the packages.config file. After the update the flag started to work and grep query returned 0 :). The best way is to compare the old .csproj file with freshly created iOS project .csproj file and see how VS is referencing nugets.
java.lang.NoSuchMethodError: org.mozilla.javascript.Parser.parse(Ljava/lang/String;Ljava/lang/String;I)Lorg/mozilla/javascript/ScriptOrFnNode;
at org.eclipse.birt.data.engine.expression.AbstractExpressionCompiler.parse(AbstractExpressionCompiler.java:238)
at org.eclipse.birt.data.engine.expression.AbstractExpressionCompiler.compileExpression(AbstractExpressionCompiler.java:132)
at org.eclipse.birt.data.engine.expression.ExpressionCompiler.compile(ExpressionCompiler.java:68)
at org.eclipse.birt.data.engine.expression.ExpressionCompilerUtil.compile(ExpressionCompilerUtil.java:56)
at org.eclipse.birt.data.engine.impl.ServiceForQueryResults.initAutoBinding(ServiceForQueryResults.java:1014)
at org.eclipse.birt.data.engine.impl.QueryResults.getResultIterator(QueryResults.java:174)
at org.eclipse.birt.report.engine.api.impl.ExtractionResults.nextResultIterator(ExtractionResults.java:157)
at org.eclipse.birt.report.designer.data.ui.dataset.DataSetPreviewer.preview(DataSetPreviewer.java:69)
at org.eclipse.birt.report.designer.data.ui.dataset.ResultSetPreviewPage$5.run(ResultSetPreviewPage.java:366)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
Getting this error while creating Dataset in Studio.
I added
rhino 1.7.7.1 jar,
updated the mysql-connector jar with the latest one.
Added jars in the project still am getting this error.
Please give some solution as soon as possible.
I searched over the internet and found that now BIRT plugins are removed from the eclipse market place so many dependency which is required for BIRT is not available even after adding SpagoBI plugins.
I downloaded "eclipse-reporting-mars-2-macosx-cocoa-x86_64.tar" for mac OS from
http://www.eclipse.org/downloads/packages/eclipse-ide-java-and-report-developers/mars2
You can easily download the eclipse for Windows,Mac or Linux OS from DOWNLOAD LINK provided in the right side.
In this IDE, Reports jars are present so you will not face any issue while creating the report or cockpit.
You just need to add the SpagoBI studio plugins in Eclipse plugin folder after that it will work without any error.
Thanks, Hope this will help.
I have a created a fresh QML quick application using Qt 5.3.2 on Mac. When I build it has 2 link errors.
Failed to parse qmlimportscanner output.:-1: error:
[iphonesimulator-debug] Error 66
I have not even made any changes to default application, why do I get these errors and how can I fix it?
I know this question is pretty old, however, as I just encountered the same error and finally managed to solve it: Your Project Path must not contain spaces for qml quick projects on ios.
Please do not ask me how or why this is the case (as it clearly works for desktop or android deployment), but this was the issue for me. After moving the project to a different location (a folder that does not contain spaces) it would run qmake and deploy just fine.
I've just moved to a new computer and imported all of my Flash Builder projects. When I try to Export a Release Build I get the following error message:
Encountered errors or warnings while building project Test.mxml.
Linked resources are not supported by this application.
I get the same message for a new project as well as for an old project. Restarting FB makes no difference. Can anyone point me to a solution?
I doubt if you really need to reinstall the OS! You might have to restart Flash Builder.. and that should clear any issues associated with cached objects etc.
Check and see if there is really something wrong with your project.. if you don't seem to find anything, create a new project - just an empty one with a button on the canvas and then try exporting a release build.
My PyQt application works fine when running on Linux, when in my Windows build environment, or frozen on the machine where it was build with py2exe. But after moving the frozen executable and its supporting files to another machine it can't load the database driver.
It worked fine when I had Python2.5 and an earlier version of PyQt and py2exe. But after upgrading my toolchain I get these errors:
dbname.open returns false
lastError(dbname) is "Driver not loaded"
I have an sqldrivers folder where I put qsqlite4.dll. This was necessary with the previous build environment, but moving or renaming that DLL doesn't change any behavior. I think that's the DLL that Qt can't find, but I haven't been able to tell Qt where to look.
I am currently running these versions:
python-2.6.3
PyQt-Py2.6-gpl-4.6-1
py2exe-0.6.9.win32-py2.6
Profiling in Dependency Walker gives me this error:
LoadLibraryW("\application\sqldrivers\qsqlite4.dll") returned NULL. Error: This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem (14001).
When I ask Dependency Walker for details about Qsqlite4.dll it says:
Error: The Side-by-Side configuration information for "\application\sqldrivers\QSQLITE4.DLL" contains errors.
That would explain why the DLL won't load, but I'm still unclear how to fix it. Closer inspection shows that error for most of the DLLs I call. Do I need to include a manifest for each Qt DLL I load?
Thanks in advance.
DEAR PEOPLE FROM THE FUTURE: Here's what we've figured out so far ...
The accepted answer doesn't really say what dlls they copied and in what places. I managed to fix it by copying the driver inside the sqldrivers directory relative to where the exe and qt dlls are (I'm using PySide but should work with PyQt4 as well). In setup.py:
setup(
...,
data_files = [('sqldrivers', ('C:\Python27\Lib\site-packages\PySide\plugins\sqldrivers\qsqlite4.dll',))],
...,
)
I solved it!
I had a really clever way to avoid making my users install vcredist--I copied the manifest and the DLLs into two places and all the errors about the MS DLLs went away. That's when I started trying to figure out this SQLite driver error.
I wasn't as smart as I thought. If I install vcredist all the "Driver Not Loaded" and "No SQL drivers found" errors go away. Arg.
Try to re-install SOLite, or verify if you have putted the DLL in the correct place, because i remember that the MySQL DLL have to be in System32 directory to develop something that uses it.
Regards.