You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
People who are facing this problem #169
For anyone getting errors while migrating to androidx, this library is androidx compatible, the way creator has added the class CustomViewPager into android.support.v4.view package confuses android studio while migrating. While migrating to androidx through the Refactor->Migrate to AndroidX, Android studio finds the package names of all the support dependencies and then converts them into their equivalent AndroidX package. So, as the CustomViewPager class is present in the android.support.v4.view support package, it converts that package name to androidx.customviewpager and then it's unable to find the class. Simple FIX: Manually add the library by downloading it and then change the package name back to android.support.v4.view wherever CustomViewPager is used! Or author can just transfer the CustomViewPager into some different package that doesn't start with android.support
The text was updated successfully, but these errors were encountered:
People who are facing this problem #169
For anyone getting errors while migrating to androidx, this library is androidx compatible, the way creator has added the class CustomViewPager into android.support.v4.view package confuses android studio while migrating. While migrating to androidx through the Refactor->Migrate to AndroidX, Android studio finds the package names of all the support dependencies and then converts them into their equivalent AndroidX package. So, as the CustomViewPager class is present in the android.support.v4.view support package, it converts that package name to androidx.customviewpager and then it's unable to find the class.
Simple FIX: Manually add the library by downloading it and then change the package name back to android.support.v4.view wherever CustomViewPager is used! Or author can just transfer the CustomViewPager into some different package that doesn't start with android.support
The text was updated successfully, but these errors were encountered: