I was trying to build an Android APK on Monaca IDE and after selecting the type (Debug/Release) a new window appears exactly with the same content (selection of build type).
After selecting (again) the build, nothing happens, only a blank screen and the build doesn’t start. The problem appears in release and debug builds.
This appear in full screen after selecting the build type on the IDE:
http://i.imgur.com/uEc7y77.png
Then, after selecting the build type again, only a blank screen:
http://i.imgur.com/bJQASjN.png
My best guess is that's a bug in the IDE and has got nothing to do with the project but for what it's worth I’m using Onsen UI V2, plain JS w/o a framework.
After a few tries and some frustation, I finally solved the problem:
exit Monaca
clear cookies (using a new Chrome user should also work)
login to Monaca
Related
I have a mac pro. I installed xamarin studio and everything I needed for android development on mac. The first time I created a project I ran it and everything works. I was able to click on a button which counted my number of clicks kind of like a default.
I decided to follow the Android quick start tutorial on Xamarin and when I got done creating the project and ran it nothing showed in my emulator. The controls I created did not show up. All I got on top of the screen was "Deployment Completed" . No error messages either. How do I trouble shoot this? I want to be able to see the screen I created in the Emulator and click on various buttons.
Now I just got an error message and it can be found below.
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets: Warning: No -tsa or -tsacert is provided and this jar is not timestamped. Without a timestamp, users may not be able to validate this jar after the signer certificate's expiration date (2047-01-01) or after any future revocation date. (Phoneword)
My guess is that your Android project did not actually get built either because you have selected the wrong configuration and platform pair or because the settings for the configuration and platform pair are not correct.
When building and running on Android, you want to make sure you change your Platform to AnyCPU and then either choose Debug or Release for your Configuration depending on what environment you are targeting. For building and running on iOS, you would just change the Platform to iPhone Simulator or iPhone.
See image below for how to access these settings (just click where the red boxes are circled):
In Xamarin Studio, with your project open:
Click Project -> Solution Options
Choose the Configurations tab
Choose the Configuration Mappings tab
Now change the Configuration dropdown to Debug and the Platform to AnyCPU
Make sure that the Build checkbox is checked next to your shared project (most likely the one at the top) and that the Build checkbox is checked next to your Android project
Now click OK, make sure you have the correct Configuration and Platform are selected
Rebuild the solution and try to run it again
*Edit: After talk in the comments, the emulator must be unlocked to actually view the running app. To unlock the emulator:
Click and hold down on the lock icon at the bottom of your emulator screen
Drag the mouse up to the top of the screen and release the click
I am interested in Spark Inspector, but i cant use it in trial mode.
I installed latest version. Then i used framework setup assistant, but it not helps.
Building settings are correct - i checked it step by step with this instructions: http://www.sparkinspector.com/framework_setup.html
I also tried to clean project and delete app from iOS simulator.
The app is for iPad, i don't know is it matter.
The error i getting is: "Setup did not complete successfully. The Spark Inspector timed out waiting for the console to settle."
I love this tool - It actually includes a wizard that lets you choose a xcode project and sets it up for inspection. try using the built in wizard.
EDIT: With version 1.3.3 of Spark Inspector, it seems it sometimes takes a while for SI to connect to the process. After you get the error, try clicking the OK button and wait for about 30 seconds. It should eventually connect. Otherwise, try some of the other tips below.
Deleting the Xcode Derived Data sometimes fixes this for me:
launch Xcode
from menubar: Xcode > preferences
click the 'Locations' tab
beneath "Derived Data" you'll see a path with a small arrow icon, click on the arrow
from the Finder window that appears, drag the 'DerivedData' folder (should be automatically selected) into the trash
quit Xcode
restart Xcode and try launching Spark Inspector again
Another thing to check is to make sure your command line tools are setup to run the same version as your current version of Xcode (happens sometimes if you have multiple copies installed at the same time like a beta):
launch Xcode
from menubar: Xcode > preferences
click the 'Locations' tab
Check the current value for 'Command Line Tools'. If it's not the same version as the Xcode version you're trying to run Spark from, then:
Select correct version
Delete the Derived Data
Quit Xcode
Restart Xcode
Clean your project (cmd-K)
Try re-running with Spark
I had the same problem. Make sure you have the dylib in the following path:
Applications/Spark Inspector.app/Contents/Resources/Frameworks/SparkInspector.dylib
I re-installed the application, force xcode to quit, re-opened xcode and the project. I've clean the project as you did and then use Product-Inspect with spark.
It takes few secondes to start after the simulator is launch. It also breaks on a line on the debugger until the inspector app is launched.
Hope this will help
We are seeing a strange behavior in our iOS part of the App:
We are using a Jenkins Build Server with an XCode plugin to compile the app on the command line
At first we had an SVN ignore on the iPhone "native" folder in our SVN. So all was taken from common and the whole native project was generated by the worklight Ant scripts on the Jenkins server. This was then compiled by the xcode on jenkins and the App worked fine with Direct Update - the Dialog had a "UPDATE" and a "EXIT" button, both buttons worked as intended.
Then we added a CustomWebView to our project and had to include the native folder into the SVN. We tried to SVN.ignore all generated files and the build processes in Worklight Studio and on the Jenkins xcode server work both fine.
We did not change any of the generated code except we added two classes:
WebViewOverlayPlugin.h
WebViewOverlayPlugin.m
and added the plugin to the config.xml:
<plugin name="WebViewOverlayPlugin" value="WebViewOverlayPlugin"/>
BUT:
when we compile the same SVN code in the Worklight Studio, we have an iPhone app that has a Direct Update dialog with only the "UPDATE" button across the whole dialog. There is no "EXIT" button anymore at all.
when we compile the same SVN on the Jenkins Xcode server, we have an iPhone app that has a Direct Update dialog with an "UPDATE" and an "EXIT" button but the "EXIT" button does not work as intended - when pressing it, the app stays open and the dialog closes, so the user can continue to use the old version of the app without updating. The "UPDATE" button works and updates the App.
So my question is, what build setting, generated files or configuration etc. could have any influence on the behavior of the Direct Update dialog. Since we use the exact same SVN source it has to have something to do with something generated, or with some configuration.
Is anything around such a strange behavior known?
Is it known that one can "configure" the Direct Update dialog to have only an "UPDATE" button with no "EXIT"?
Thank you all for any help or hint where we could look to further investigate.
You didn't mention your Worklight version, but starting with Worklight 5.0.6.x:
The Direct Update dialog will feature only 1 button - Update. The Exit button was removed.
This was done in order to be inline with Apple's App Store submission guidelines.
And more in general, the WL.App.close API method was rendered "non functional", because as per Apple's guidelines, it is the user that should be given the control on exiting the application and not the application to do so. Think of it as an "OK" button instead of "Exit".
That said, you are not supposed to see an Exit button to begin with. But again, I do not know what is your Worklight version and what exactly is your build setup to understand what is going on there that does this sort of mixing.
You are not supposed to be able to "configure" anything in Direct Update. It is non-configurable in this respect.
As for why you have 2 buttons when building with Worklight Studio, but 1 button after adding the WebOverlayPlugin, it is interesting. Is there a chance the app is of a lower Worklight version and you are now building it with a newer version of Worklight, containing the changes made, as described above?
I just set up a new PhoneGap project for android, which worked perfectly fine without any problems, there were almost no changes to the template project.
Then I wanted to move that exact project to iOS, and the woes began.
When I start the project, suddenly a bunch of alter dialogs pop up, with device information, network status. Each offer me "ok" and "cancel". When I press "ok" on any of them, execution is halted, and nothing happens further.
When I cancel them all, I get to the project screen, where it says "connecting to device". Obviously, deviceready is never fired on this.
Since this project is merely the template offered by Cordova themselves, I find it hard to believe it is not supposed to run. I suspect the console.log messages get popped up on screen rather than the XCode debug window.
I am completely new to XCode or any iOS programming (hence PhoneGap), and I would appreciate any help.
Using Cordova 2.8.1.
Reason was I mistakenly copies the cordova.js for android into the ios project, see here.
Yesterday I was able to build apk files.
Since I have add lots of pictures and ressources to theme the app, and when I want to test it on my device, Visual Studio build me one app that crash.
I set the "Release" mode, I go to TOOL>Publish application, I create a keystore and I build the apk.
I put the code to "Disable Debugging" and I've made the manifest.
When I tried to install it, it works, but the app crash.
The application works perfectly with the emulator.
The weight hasn't really change (some Ko) but the app MUST be bigger because of all the pictures I've put, so something is wrong...
Thanks to help me :-)
I unchecked the "Use Shared Runtime" in the properties>Mono android options: