🎉 The Solution: @StateObject keeps your view model as loyal as a dog, sticking around no matter how many times the view redraws.

🧠 Key Takeaways:

1️⃣ Use @StateObject when you create the ObservableObject inside the view

2️⃣ Use @ObservedObject for objects passed into the view

3️⃣ @StateObject ensures object lifecycle tied to the view lifecycle

4️⃣ @ObservedObject assumes external lifecycle management

💡 Pro Tips:

· @StateObject is like a lazy var for ObservableObjects in SwiftUI

· Only use @StateObject in one place to avoid lifecycle conflicts

· @Published properties auto-trigger view updates (or use objectWillChange.send() manually)

🚀 Remember: @StateObject saves you from unexpected resets in complex view hierarchies!

Found this enlightening? Let's connect and explore more SwiftUI intricacies!

hashtag#SwiftUI hashtag#iOSDev hashtag#StateObject hashtag#ObservedObject hashtag#CodingTips

Hello Everyone,

Continue reading on helloParithi »

Hey guys, Welcome back!

Continue reading on helloParithi »

:app:transformClassesWithJarMergingForDebug'.
com.android.build.transform.api.TransformException: java.util.zip.ZipException: duplicate entry: 
/some/package/name/containing/SomeClass.class

Are you facing this error on your Android Project too?

I tried a few things to fix this,

First, I tried to clean up the dependencies based on a few sources from StackOverflow. To do this, Goto your project’s root folder and run the following :

./gradlew clean

But that didn’t help me out.

The Solution that worked,

This error is likely to occur if two or more of your dependencies have the same class in the package as other packages. To find that out, You could run the following command from your root project folder :

./gradlew dependencies

Or you can install the plugin “Android Methods Count”, by going to Android Studio > Preferences > Plugins. Type “Android Methods Count” and click “browse” below. On the popup that opens up, Click “Android Methods Count” and click “Install Plugin” at the side.

This will enable you to view the dependencies that your dependencies depend upon and will help you to exclude the dependencies that may have already added.

A clue would be the class path that you get in the error :

:app:transformClassesWithJarMergingForDebug'.
com.android.build.transform.api.TransformException: java.util.zip.ZipException: duplicate entry:
com/google/common/base/FinalizableReference.java

In the error that I’ve got, we could see that the “FinalizableReference.java” is a part of the Guava Library by Google. To rectify this error, we need to look up for the dependencies that use the guava library and exclude it.

To find that out, goto your build.gradle file and check the dependencies by hovering over the blue circle to the left of th “compile…” code blocks. A tooltip will popup with the dependencies that are you used by your dependency package. In my case,

As you can see here, ‘com.google.apis:google-api-services-youtube:v3-rev175–1.22.0’ is using the module ‘guava-jdk5’. So by excluding that module,

compile ('com.google.apis:google-api-services-youtube:v3-rev175-1.22.0'){
    exclude module: 'guava-jdk5'
}

By excluding this, I was able to fix this error.

Hope this helps you in rectifying yours. Let me know in the comments if you have any questions.

Happy coding :)

Solution for TransformException was originally published in helloParithi on Medium, where people are continuing the conversation by highlighting and responding to this story.

Stack for this web app requires that it should run on Tomcat 7 and therefore we had write them as Java Servlets. We need the Google Vision API to determine whether the image is suitable by checking whether the labels returned by the API are congruous with a set of predefined tags that we have. To add the Google Vision API, we added the following to our maven ‘pom.xml’ :

<dependency>
    <groupId>com.google.cloud</groupId>
    <artifactId>google-cloud-vision</artifactId>
    <version>0.17.2-beta</version>
</dependency>

and Bam! I got the following error popping up from within the Google API on runtime:

Jetty ALPN/NPN has not been properly configured

Google API uses the HTTP/2 protocol for executing which is still not supported by the old Tomcat servers. In order to fix this, we need to configure an ALPN client that matches our JDK version for our project.

You can read more about it in the following link :

Chapter 15. Application Layer Protocol Negotiation (ALPN)

To fix our issue, we need to download the appropriate ALPN client (I downloaded a jar file) from the maven repository here (Version — 8.1.4.v20150727 as my JDK version was 1.8.0u51) :

Maven Repository: org.mortbay.jetty.alpn " alpn-boot " 8.1.4.v20150727

After downloading the jar, you need to go to the Tomcat Server settings in eclipse and add the ALPN jar file as one of the bootstrap entries for your server. Find a similar way to add it to your classpath if you are using any other IDE.

That should fix the issue, you should probably getting it working after you add this.

During Deployment :

Add the alpn-client jar to a folder and add it to the $CLASSPATH of your tomcat server. I’ve set the $CLASSPATH at /usr/local/apache-tomcat-XXXX/bin folder where I’ve created a file called ‘setenv.sh’ and this is what it contains:

CATALINA_OPTS="-DGOOGLE_APPLICATION_CREDENTIALS=/home/parithi/google_credentials.json"

CLASSPATH="$CLASSPATH:/home/parithi/MY_PROJECT_FOLDER/:/home/parithi/alpn-boot-7.1.3.v20150130.jar"

Thanks for your time, if you have any questions, feel free to leave a comment below. And if this article helped you out, please show your support by hitting the like button.

Jetty ALPN/NPN has not been properly configured — Solution was originally published in helloParithi on Medium, where people are continuing the conversation by highlighting and responding to this story.

The rise of Augmented Reality apps are gaining momentum in all fields these days and it’s good to have some experience building them. And…

Continue reading on helloParithi »

Hey guys!

If you are working with recycler views on Android, you might be encountering this dreaded error: IndexOutOfBoundsException — Inconsistency detected. Invalid Item ## Item Position, etc. Let’s see a few ways to fix this.

Understand why this happens

When the user scrolls your recycler view while the data is being changed on the list (maybe because you are adding/removing elements in the background because of pull to refresh or because of pagination or some background sync process), the ViewHolder loses the reference to the item on the recycler view and the item on the data list.

Solutions

1. Make sure you are finished with updating the data on the list and only then, on the main thread, notify the recycler view’s adapter using notifyDataSetChanged() .

2. If you are modifying the list using the .add() , addAll() , remove() , removeAll() , make the process is synchronized before notifying the recycler view’s adapter. (Or) Create a temporary list to contain your new data and set it directly to your main list attached to your adapter.

Example, if you are modifying your list like this :

val dataList : MutableList<Person> = listOf() // --> used by your recyclerview for showing the list
..
..
val personData = getPersons()
..
..
dataList.addAll(personData())
dataList.add(Person(name="Parithi"))
..
..
recyclerView.adapter?.notifyDataSetChanged()

Change the code into this :

val dataList : MutableList<Person> = listOf() // --> used by your recyclerview for showing the list
..
..
// create a temporary list
val temporaryList : MutableList<Person> = listOf() 
val personData = getPersons()
..
..
temporaryList.addAll(personData())
temporaryList.add(Person(name="Parithi"))
..
..
dataList = temporaryList // set it to the main list
recyclerView.adapter?.notifyDataSetChanged()

Solutions that may work but not recommended — will affect UI experience

1. Clear the recyclerview’s cache usingrecyclerView.getRecycledViewPool().clear();

2. Disable the scrolling on the recycler view when the data is being updated by overriding the onTouch.

Hope this article, helped you fix the issue. Thanks for reading and Happy Coding :)

RecyclerView — IndexOutOfBoundsException — Inconsistency detected was originally published in helloParithi on Medium, where people are continuing the conversation by highlighting and responding to this story.

This nifty trick is actually from MacRumors but unfortunately, this valuable tip has a dead link on their website. The MacBook Air’s…

Continue reading on helloParithi »

When I was doing my PG diploma on Game Development at ICAT, I used to wonder at the lack of really good games made by Indian game studios…

Continue reading on helloParithi »

We’ve all been to that point where we had to send more than 10 media files (photos, audio, video, documents) from our Photos App on our iPhones or while forwarding a bunch of such files we got from a contact to another.

And you might have noticed that Whatsapp’s share functionality gets disabled when you tried to forward more than 10 messages containing media or that the Whatsapp icon doesn’t appear when you try to share those files from the Photos App.

Well, there’s a workaround.

Please note :

1. This will only work as long as the Whatsapp Team hasn’t fixed this issue.

2. This will only work only if you received the media files from another contact or when you have send those files to someone.

3. This works only in iOS.

Solution

To this working,

1. Open the contact in Whatsapp to whom you have sent the files to / received the files from.

2. Click on ‘Media, Links and Docs’.

3. Here you can click on all the items that you want to forward and then press the ‘Share’ button on the bottom.

4. Scroll the apps on the list and you can find ‘Forward XX messages’ with the Whatsapp icon.

5. And thats it! Enjoy!

How to send more than 10 media files on Whatsapp (iOS) was originally published in helloParithi on Medium, where people are continuing the conversation by highlighting and responding to this story.

Update for Windows 8/10 users : The download which I’ve given doesn’t seem to work on a few games that are running in Windows 8. If you…

Continue reading on helloParithi »