I'm trying to upload my bundle using Application loader but I get an error about the Icon not being properly set in info.plist
And indeed: my info.plist does not contain any app icon settings but I configured the items in MonoDevelop and they show up correctly in simulator and on the iPad.
It is a universal which currently supports iPad only. What am I supposed to define in my info.plist?
You shouldn't have to edit your plist directly. The settings you make in MD should populate the plist for you automatically. You can look inside the app bundle generated by MD to verify that this is really happening.
You might also verify that your icon is in the root of your project (not a subfolder) and that you have the casing of the name corrected. I think that the simulator is more forgiving of improper casing than the real device.
Related
I uploaded an extension to the project from the shopware admin panel. The extension is active and I can set the configurations. The problem is the module doesn't show up under Settings > Extensions. How can I fix this problem?
It would be helpful to know which module you are talking about.
Anyways, each module you install should appear under Extensions -> My Extensions and you can configure basic settings (those which are added by the developer via config.xml) in the extension list, ...-menu and then "configuration". I assume think that is already working in your case.
If the module you installed did not add extended configuration capabilities, then it will not be visible under Settings -> Extensions - so this is completely normal and not an error.
If you are developing that module and need extended settings, you have to add them via a VueJS / javascript module. This works roughly the same as adding pages anywhere else in the admin panel.
Like Alex said, the configuration options do not appear by default under Settings -> Extensions for any given plugin.
If you want to add something like this to your plugin, you're going to have to specify a settings item in your JS module, looking like this
settingsItem: [{
group: 'plugin',
to: 'my.custom.route',
icon: 'my-plugin-icon',
name: 'my.custom.settings.title'
}]
Of course, you are going to need a page for my.custom.route.
A working example of both can be seen in the module registration file and page registration file of the FroshPlatformAdminer plugin
I'm following Liferay getting-started example to develop my first we app with Liferay IDE in which it is mentioned:
Even though all you’ve done is generate it, the guestbook-web project is ready to be built and deployed to Liferay DXP. Make sure that your server is running, and if it isn’t, select it in Developer Studio’s Servers pane and click the start button. After it starts, drag and drop the guestbook-web project from the Project Explorer to the server.
I started the server, however, I don't know how to deploy guestbook-web module to server. Drag and drop is not working for me:
When Opening the web page, this is shown which doesn't contain anything related to guestbook-web module:
Update
When I drag and drop my module on server, for some reason it is not allowed:
Update
Also, I'm receiving such errors on console:
22-Apr-2020 16:02:54.419 SEVERE [http-nio-8080-exec-6] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [Module Framework Servlet] in context with path [] threw exception [PWC6345: There is an error in invoking javac. A full JDK (not just JRE) is required] with root cause
org.apache.jasper.JasperException: PWC6345: There is an error in invoking javac. A full JDK (not just JRE) is required
I have set both JDK and JRE path for IDE, not sure why it says A full JDK (not just JRE) is required.
Update
To fix A full JDK (not just JRE) is required error, inspired by this answer, I ran the IDE with this command:
C:\Program Files (x86)\LiferayWorkspacewithDevStudioCommunityEdition\liferay-developer-studio>DeveloperStudio.exe -vm "C:\Program Files\Java\jdk1.8.0_251\bin\javaw.exe"
The error is resolved and default widgets are fine now:
In the IDE: You'll drag the "guestbook-web" with the mouse and drop it right on the highlighted "Liferay 7.x at localhost" Server (Note: on, not below).
Outside of the IDE: Your project generates a jar, and you can copy that to Liferay's deploy directory.
Once the module is deployed, it won't magically show up on the page: Log in as Administrator, choose the "Add" button (a plus sign) and add a "widget" to the page: In the list of Widgets you'll find your new portlet/widget.
The screenshot of your installation looks weird though, as if something didn't go wrong and you'll likely need to look for signs of problems in the log file to see why Liferay ends up in the state that it's in, with a couple of default widgets being unavailable - however, that's unrelated to the question how to deploy new code to the runtime.
Edit: You've mentioned the required JDK from the log. That's good to be fixed.
With regards to the not-working drag&drop: It looks like you're using Liferay Workspace. From the icons in Project Explorer, it looks like your module isn't recognized as such: Try to "Gradle/Refresh Gradle Project" (right-click on "modules") to see if it needs some updates that are missing (and observe its log output). Icons on my IDE look like this:
Once you get those modules recognized, you should be able to drag&drop them to the server.
I realized to avoid A full JDK (not just JRE) is required error, it is needed to setup server correctly while creating it with GUI:
I want to debug my React.js project by adding breakpoints in WebStorm rather than in my web browser.
Is it possible? If yes, how?
Run npm start to get the app running in the development mode.
You can do this either in the terminal or by double-clicking the task in the npm tool window in WebStorm.
Wait till the app is compiled and the Webpack dev server is ready. Open http://localhost:3000/ to view it in the browser.
Create a new JavaScript debug configuration in WebStorm (menu Run – Edit configurations… – Add – JavaScript Debug). Paste http://localhost:3000/ into the URL field.
In WebStorm 2017.1+
No additional configuration is needed: go to step 5!
In WebStorm 2016 (.1, .2 and .3)
Configure the mapping between the files in the file system and the paths specified in the source maps on the dev server. This is required to help WebStorm correctly resolve the source maps.
The mapping should be between the src folder and webpack:///src
If you’re wondering how we got this mapping, check http://localhost:3000/static/js/bundle.js.map file. This is a source map file for the bundle that contains the compiled application source code. Search for index.js, the main app’s file; its path is webpack:///src/index.js
Save the configuration, place breakpoints in your code and start a new debug session by clicking the Debug button next to the list of configurations on the top right corner of the IDE.
Once a breakpoint is hit, go to the debugger tool window in the IDE. You can explore the call stack and variables, step through the code, set watcher, evaluate variables and other things you normally do when debugging.
This app is using Webpack Hot Module Replacement by default and that means that when the dev server is running, the app will automatically reload if you change any of the source files and hit Save. And that works also together with the WebStorm debugger!
Please take note of these known limitations:
The breakpoints put in the code executed on page load might not be hit when you open an app under debug session for the first time. The reason is that the IDE needs to get the source maps from the browsers to be able to stop on a breakpoint you’ve placed in an original source, and that only happens after the page has been fully loaded at least once. As a workaround, reload the page in the browser.
Webpack in Create React App generates source maps of the type cheap-module-source-map. This kind of source maps do not guarantee the most precise debugging experience. We recommend using devtool: 'source-map' To make changes to the app’s Webpack configuration, ‘eject’ the app (refer to the Create React App manual to learn more).
From this diagram I understand that the last step of the bootup process has the window manager launching the Gaia home screen.
I want to experiment and change the the first app that is booted and whatever launches when the home button is pressed, but I have not been able to figure out exactly where is that the homescreen app first launched.
Any pointers would be greatly appreciated.
There is a setting called homescreen.manifestURL that points to the manifest URL of the application that is used as homescreen. You can grep this string to know where exactly it's used.
This setting is set at build time in build/settings.js. You can try to change it there.
You can also install a separate homescreen app (see https://github.com/KevinGrandon/firefoxos-homescreen-boilerplate for a boilerplate for a homescreen -- I'm not sure how uptodate it is) and enable it from the Settings app. It has a "role": "homescreen" property in its manifest.
I understand the need to provision apps when you are getting close to deployment; however, right now, I am just trying to play with some sample code. Specifically, the GKRocket demo that ships with iOS 4.2 SDK. I want to compile and run it; however, I get the following error:
Code Sign error: a valid provisioning profile matching the application's Identifier 'com.apple.GKRocket' could not be found
The readme.txt claims "Build the game simply by opening it with Xcode and clicking on Build and Go."
I just read the following thread
Code Sign Error When Building iPhone Application
and the following
http://developer.apple.com/ios/manage/bundles/index.action
Since the app is using the NSNotificationCenter, it leads me to believe that I need an AppID. But shouldn't the demo already be pointing to and AppID setup by Apple for the demo code?
The plist shows
Bundle identifier com.apple.${PRODUCT_NAME:rfc1034identifier}
any ideas on what I should do to compile and run this in the simulator?
Update:
I was able to get it running by code signing, but never could compile without it :(
It appears since the GKRocket Demo is using the NSNotification Center that in fact you need to sign your code. You can sign your code with your/or your team cert. Change the Project -> Project Settings -> Code Signing Identity to use your cert. Note: If you don't have your cert, and you paid the $99 dev license go through the steps here.
Then open the plist file and change the bundle to your domain name.
Also, to get the GKRocket Demo running, make sure you turn on Bluetooth in your network settings.
System Preferences -> Bluetooth. Turn it on and check discoverable. Then go into advanced settings
Install your app on your iPhone with a build and run. Close the debugger. Then start your app in the local iOS simulator. Now manually run your app on your phone.