Received 403 from server (Forbidden) - maven

Please i need someone to help me out of this, am new, I got these error while trying to build apk
Could not GET 'http://dl.bintray.com/jlmd/maven/com/faltenreich/skeletonlayout/2.0.1/skeletonlayout-2.0.1.pom'. Received status code 403 from server: Forbidden
along side this error:
Disable Gradle 'offline mode' and sync project
[Error .apk]

New location to toggle Gradle's offline mode To enable or disable
Gradle's offline mode, first select View > Tool Windows > Gradle from
the menu bar. Then, near the top of the Gradle window, click Toggle
Offline Mode Gradle offline button in the Gradle panel..

Please check first whether Offline mode is truly deactivated via Help / Find Action...: Type "offline mode" into the dialog and check whether "Toggle Gradle Offline Mode" is set to "Off". If it was set to "On", toggle it and try syncing again.
If this does not work, the problem might have something to do with the sunset of JCenter. Try a more current version of this library, e.g. com.faltenreich:skeletonlayout:4.0.0 which is hosted on MavenCentral (mavenCentral())and remove JCenter (jcenter()) from your repositories. Then try syncing again.
Disclaimer: Am developer of the library from the error message

Related

Test in cloud button has gone

I made a 'Xamarin UI Test' Project to test my app.
I was able to click in the button like this: Run in Test Cloud button.
But now i made my test using the Repl() and want to run it in the cloud the button has gone away.
What i have to do to fix it?
Cause of the Issue
It looks like you are hitting this bug: Bug 52372 - "Run in Test Cloud" option no longer appears in menu on C9
That issue is reported on this version for Xamarin 4.3.0.636. Note that it may happen in other versions but this is the initial version the bug was reported against. You can track the status of that issue either directly in the report on Xamarin's bugzilla, and/or you can watch for a release announcement on the Xamarin Releases Blog.
Workarounds
Downgrading Xamarin
While waiting for a fix to become available, you can downgrade to the previous Cycle 8 version of Xamarin by going to “Get the latest stable version of Cycle 8” section on your account page: https://store.xamarin.com/account/my/subscription/downloads#cycle8.
Uploading to Test Cloud via the Command Line
Alternatively, you can upload tests to the Test Cloud through the command line. To do this log into https://testcloud.xamarin.com & click "New Test Run" at the top. (Note this option is only visible if you have a currently valid Test Cloud account or trial.)
This launches a wizard which will have you pick some options (like whether you want to use Android or iOS; etc.), and at the end will generate a prototype command line. Below is an example for Android:
packages\Xamarin.UITest.[version]\tools\test-cloud.exe submit yourAppFile.apk [API_KEY] --devices [DEVICE_HASH] --series "master" --locale "en_US" --user [EMAIL] --assembly-dir pathToTestDllFolder
Note: I have removed the [API_KEY], [DEVICE_HASH] & [EMAIL] values for privacy reasons, however these will automatically be included when you generate the prototype from the wizard in Test Cloud.
You will still have to manually update the Xamarin.UITest.[version] as well as the actual names and relative paths of yourAppFile.apk & pathToTestDllFolder for this approach to work.

sandbox fail to access local socket

i've created a local socket in my app, and i'm getting the following error when trying to send data to target process :
deny network-outbound
i've made some research and found out that in order to fix this problem on Xcode based application, i need to to set "Allow Outgoing Network Connections" checkbox in the Summary tab of the target editor.
however, i'm using Xcode 6.3.2 and i don't see such option (summery tab is also missing).
where can i get the equivalent of this checkbox?
This is Xcode 6.4, but it was the same in 6.3.2:

Why does WebStorm's LiveEdit not work in Chrome?

I am exploring WebStorm's trial version and would like to use the LiveEdit features.
I am not able to use the LiveEdit features after performing the following actions:
Made sure that LiveEdit is turned on
Installed the Chrome extension
Restarted the browser after installing the extension (I still suspect it is not required)
Run the HTML page in chrome
When I modify the HTML body, I don't see the changes reflected in Chrome.
I read on a forum that netty is not required.
Do we need it?
What else do I need to configure so that I can use the LiveEdit feature?
PS: I am using WebStorm 5.0.
Do you happen to have IntelliJ open by chance?
The point is that the port, 63342, is 'seized' by another app (even if it has nothing to do with HTML debugging).
When the port is busy, LiveEdit tries the next one, 63343. If you right click the JB icon on Chrome, choose Options, increment the port by one, and press Apply, you will magically connect. I wish Jetbrains would have bothered to inform the user what is the port that they are currently attempting to use.
In my PC it happened when I had Mac on. Either one of the following worked:
1. Kill IntelliJ IDEA (that was also open) and try again
2. Increment the port by one as I mentioned above.
I had to go to Run -> Debug (CTRL+F5 on Windows)
What helped in my case was activating "Can accept external connections" under the Settings -> Build, Execute, Deployment -> Debugger
WebStorm Settings
More details as requested:
Installed the JetBrains IDE Extension for Chrome
Make sure the LiveEdit Plugin is installed and activated (Settings -> Plugins)
Make sure "Can accept external connections" is checked (Settings -> Build, Execute, Deployment -> Debugger) AND Port is the same as in the Chrome Extension
Make sure Update ist set to "Auto in (ms)" e.g. 300 (Settings -> Build, Execute, Deployment -> Debugger -> Live Edit)
In my case live edit was just disabled (for some reason)
For anyone googling this thread, LiveEdit is now supported without a plugin. Just go into settings and uncheck "Use JetBrains IDE Support extension for debugging and Live Edit".
Without the extension, the debugging and live edit are more reliable based on my personal experience.
I couldn't make Chrome and Webstorm to link with each other. Chrome plugin was set to 63343 port or something like that.
I am on Windows. I opened command line with administrator privileges and typed:
netstat -a -b
to see all programs and ports they are listening to. I then found first entry regarding WebStorm.exe and saw that it was listening on port 30897. I set that port number in my chrome plugin options, and everything worked.
A quick fix: in the Chrome addon configuration, use the ip 0.0.0.0 for the host.
Turning off the automatic connection configuration from Internet Explorer properties worked for me smoothly. IE is the boss.

How to debug play2 in idea?

I found some articles on the internet and some discussions on google group, but they don't work any more.
How to do it with the latest play2-RC3 ?
You can start the play server in debug mode from console [docs], and should be able attach a debugger instance from Idea given that you know the port debugger is listening on.
I haven't use Idea so not sure if it is doable or not. It is fairly easy from netbeans. I suspect, it should be similar from Idea.
EDIT: They have also posted this in their customization guide for IDEs.
Debugging Play 2.x is very easy with IntelliJ IDEA 12.x, here are the steps you have to do:
Step 1. Enable the Play Framework Support plugin and the Play 2.0 Support plugin in File > Settings > Plugins.
The generic plugin usually comes with IntelliJ but make sure it's enabled. The Play 2.0 Support plugin can be downloaded by clicking Install Jetbrains plugin.... Simply locate and install the plugin from the list, the latest working version for 12.x is v.0.2.49. (it may prompt that a Scala plugin needs to be installed aswell)
Step 2. Create a new Play app if you haven't or use an existing one
Step 3. Create a new Debug configuration: Run > Edit configurations...
You can click the + icon in the top left corner to add a new configuration. Simply select Play 2 app from the list and give the configuration a name. The default options should be correct but feel free to change them if necessary. When done, click Apply and Ok.
Step 4. Your toolbar should now have a Run icon and a Debug icon enabled.
Simply click the green arrow to run the Play application. This is the equivalent of doing play run from the commandline (except without the commandline).
To debug, click the green bug, next the the arrow. This is the equivalent of doing play debug from the commandline.
You will now be able to debug when a breakpoint is encountered.
Notes:
Make sure there is only 1 configuration running at a time because Play doesn't like multiple instances running at the same time.
If you're having trouble compiling, do a play clean-all and play package on the commandline, this should resolve most problems. If there are further problems, also try play idea from the commandline.
Make sure the Play configuration is filled in in your settings. You can do this by going to File > Settings > Play Configuration.
A video of these steps can also be found in this video by James Ward (start at around 1:40 min.).
Go to Run -> DEBUG -> Edit Configurations
use "Remote" Configuration and set the Port to 9999

How to lock "Run" button in TeamCity

I made a build in TeamCity which deploys code to live server. As a precaution I want to disable that button "run" can be clicked by mistake.So I want to have an additional level of checking "whether I'm sure" I want to click "run" button. Is it possible to accomplish?
Thanks in advance!
I don't think there is a way to disable the run button.
An approach I've used is to have a Property which gets passed to the build script which needs to be true for the script to run, it's false or not set then the build script throws an error. Then in the build configuration on the Properties & Environment Variables page I set the property to false. Now whenever I need to run the script I have to use the "Run custom build" button (the "| ..." bit beside the run button), then I set the value to true before hitting the build button.
Another, easier option, is to add a agent requirement to your build such that only the production server's agent can meet it (e.g. env.COMPUTERNAME equals MyProductionServer01), and then disable the agent with a note about "locking" the production build. This will prevent the build from actually running if you accidentally click the Run button.
You cannot disable the run button but you can set permissions so that people are still able to view the project without the ability to run it (specifically the Run Build role).
As far as the confirmation goes there is nothing built into TeamCity to accomplish this but I do believe it would be possible to write a small plugin to gain this type of functionality.
Plugin Information:
http://confluence.jetbrains.net/display/TCD6/Developing+TeamCity+Plugins
Indeed, there is no ability to hide Run button unless the build configuration is placed in a different project, which user has no permission to run builds in.
There is a related feature request in TeamCity issue tracker.
As to requesting confirmation, there is still no direct support, but since TeamCity 7.0 one may add a parameter with mode "prompt" and this will result in the run custom build dialog popping out on Run button click.
We have solved this by providing double log-ins for our users. The normal user is not having permisson to run dangerous projects, but if the log in as elevated.user they have access to the run button for these projects as well.
So in normal situations there is no risk of running by accident.
I don't think there is disable button for run. You can pause the build and run it when you want to deploy to live sever.
Not that I'm aware of. If you have enterprise you could set it up so that there is a special account which has permissions to execute that build. Another workaround would be to make the build look at a specific branch in your SCM repo with restricted permissions, etc. Typically merging to a branch requires a bit of effort so its not as easy as hitting run by accident. Also ensures that someone hitting run won't necessarily grab the latest unstable copy from the trunk or somesuch.
You can now remove the Run button by adding teamcity.ui.runButton.caption parameter with an empty value.
See this comment on YouTrack.

Resources