In my current project at work, I had to setup a private maven repository hosted at Artifactory. I was assigned login credentials to access the libraries (or artifacts) from the repository. But, when I was fetching it from Android Studio project through build.gradle file, I was getting this exception on syncing the project.
org.gradle.internal.resource.transport.http.HttpRequestException: Could not GET 'MY_MAVEN_ARTIFACT_URL_GOES_HERE'. Caused by: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) at java.
In the recent Google IO 2018 event held in May 2018, Google recommended developers to update to latest Android APIs after August 1, 2018. So, this article is a big big reminder for this announcement. > # August 1 has passed and all the new android apps on Google Play should target API Level 26 (Android Oreo) in order to be published.
But Why? Why should I update it? Well simple answer is: boss’s orders.
Kotlin supports a technique called conventions, everyone should be familiar with. For example, if you define a special method plus in your class, you can use the + operator by convention: That’s called Kotlin Operator Overloading.
In this article, I want to show you which conventions you can use and I will also provide a few Kotlin code examples that demonstrate the concepts. Kotlin defines conventions that we can apply by implementing methods that comply with predefined names like plus.
When we use Fragment in our app, we often time need access to Context or Activity. We do it by calling methods such as getContext() and getActivity() methods. But, in kotlin, these methods return nullables and we end up using code like this.
fun myTempMethod() { context?.let { // Do something here regarding context } // Or we do it like this var myNonNullActivity = activity!! } For example, we need Activity in asking permissions.
At my current project at work, I have a situation to add a third-party library locally instead of fetching it from jCenter or JitPack.io. So, my first task is to download AAR or JAR file of the library. The reason of using AAR/JAR is to avoid compiling of library on each build of the project to decrease build time.
Here’s how First, you need to include it in your project using traditional way of implementation as you do with Android Studio.
Few days ago, I launched an Android library called as Medium Clap, which allows developers to create Medium clapping effect in Floating Action Buttons with few lines of the code.
The library went on to be featured in different android newsletters and became #1 on Github Trending in Kotlin.
But, one question which I was being asked over and over again was how to publish android libraries, especially those written in Kotlin, on jCenter.
A lot apps use Retrofit or OkHttp for the networking, and when it comes to testing the networked operations, then it becomes a little tricky. As network calls can take a little time, and test fails early due to the delay. In such cases, Idling Registry is used for testing.
If you are using Retrofit or OkHttp, then there’s this OkHttp Idling Resource which makes testing idling resources and network calls a lot more easier with few lines of code.
