UNPKG

react-native-fetch-calendar-events

Version:
132 lines (118 loc) 8.97 kB
<?xml version="1.0" encoding="UTF-8"?> <issues format="4" by="lint 25.2.2"> <issue id="InvalidPackage" severity="Warning" message="Invalid package reference in library; not included in Android: `java.nio.file`. Referenced from `okio.Okio`." category="Correctness" priority="6" summary="Package not included in Android" explanation="This check scans through libraries looking for calls to APIs that are not included in Android. When you create Android projects, the classpath is set up such that you can only access classes in the API packages that are included in Android. However, if you add other projects to your libs/ folder, there is no guarantee that those .jar files were built with an Android specific classpath, and in particular, they could be accessing unsupported APIs such as java.applet. This check scans through library jars and looks for references to API packages that are not included in Android and flags these. This is only an error if your code calls one of the library classes which wind up referencing the unsupported package."> <location file="/Users/develops/.gradle/caches/modules-2/files-2.1/com.squareup.okio/okio/1.6.0/98476622f10715998eacf9240d6b479f12c66143/okio-1.6.0.jar"/> </issue> <issue id="OldTargetApi" severity="Warning" message="Not targeting the latest versions of Android; compatibility modes apply. Consider testing and updating this version. Consult the android.os.Build.VERSION_CODES javadoc for details." category="Correctness" priority="6" summary="Target SDK attribute is not targeting latest version" explanation="When your application runs on a version of Android that is more recent than your `targetSdkVersion` specifies that it has been tested with, various compatibility modes kick in. This ensures that your application continues to work, but it may look out of place. For example, if the `targetSdkVersion` is less than 14, your app may get an option button in the UI. To fix this issue, set the `targetSdkVersion` to the highest available value. Then test your app to make sure everything works correctly. You may want to consult the compatibility notes to see what changes apply to each version you are adding support for: http://developer.android.com/reference/android/os/Build.VERSION_CODES.html" url="http://developer.android.com/reference/android/os/Build.VERSION_CODES.html" urls="http://developer.android.com/reference/android/os/Build.VERSION_CODES.html" errorLine1=" targetSdkVersion 22" errorLine2=" ~~~~~~~~~~~~~~~~~~~" quickfix="studio"> <location file="/Users/develops/Projects/pwc/react-native-fetch-calendar-events/android/build.gradle" line="24" column="9"/> </issue> <issue id="SimpleDateFormat" severity="Warning" message="To get local formatting use `getDateInstance()`, `getDateTimeInstance()`, or `getTimeInstance()`, or use `new SimpleDateFormat(String template, Locale locale)` with for example `Locale.US` for ASCII dates." category="Correctness" priority="6" summary="Implied locale in date format" explanation="Almost all callers should use `getDateInstance()`, `getDateTimeInstance()`, or `getTimeInstance()` to get a ready-made instance of SimpleDateFormat suitable for the user&apos;s locale. The main reason you&apos;d create an instance this class directly is because you need to format/parse a specific machine-readable format, in which case you almost certainly want to explicitly ask for US to ensure that you get ASCII digits (rather than, say, Arabic digits). Therefore, you should either use the form of the SimpleDateFormat constructor where you pass in an explicit locale, such as Locale.US, or use one of the get instance methods, or suppress this error if really know what you are doing." url="http://developer.android.com/reference/java/text/SimpleDateFormat.html" urls="http://developer.android.com/reference/java/text/SimpleDateFormat.html" errorLine1=" SimpleDateFormat sdf = new SimpleDateFormat(dateFormat);" errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~"> <location file="/Users/develops/Projects/pwc/react-native-fetch-calendar-events/android/src/main/java/com/calendarevents/CalendarEvents.java" line="99" column="32"/> </issue> <issue id="SimpleDateFormat" severity="Warning" message="To get local formatting use `getDateInstance()`, `getDateTimeInstance()`, or `getTimeInstance()`, or use `new SimpleDateFormat(String template, Locale locale)` with for example `Locale.US` for ASCII dates." category="Correctness" priority="6" summary="Implied locale in date format" explanation="Almost all callers should use `getDateInstance()`, `getDateTimeInstance()`, or `getTimeInstance()` to get a ready-made instance of SimpleDateFormat suitable for the user&apos;s locale. The main reason you&apos;d create an instance this class directly is because you need to format/parse a specific machine-readable format, in which case you almost certainly want to explicitly ask for US to ensure that you get ASCII digits (rather than, say, Arabic digits). Therefore, you should either use the form of the SimpleDateFormat constructor where you pass in an explicit locale, such as Locale.US, or use one of the get instance methods, or suppress this error if really know what you are doing." url="http://developer.android.com/reference/java/text/SimpleDateFormat.html" urls="http://developer.android.com/reference/java/text/SimpleDateFormat.html" errorLine1=" SimpleDateFormat formatter = new SimpleDateFormat(" errorLine2=" ^"> <location file="/Users/develops/Projects/pwc/react-native-fetch-calendar-events/android/src/main/java/com/calendarevents/Utility.java" line="45" column="38"/> </issue> <issue id="GradleDependency" severity="Warning" message="Old buildToolsVersion 23.0.1; recommended version is 23.0.3 or later" category="Correctness" priority="4" summary="Obsolete Gradle Dependency" explanation="This detector looks for usages of libraries where the version you are using is not the current stable release. Using older versions is fine, and there are cases where you deliberately want to stick with an older version. However, you may simply not be aware that a more recent version is available, and that is what this lint check helps find." errorLine1=" buildToolsVersion &quot;23.0.1&quot;" errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~" quickfix="studio"> <location file="/Users/develops/Projects/pwc/react-native-fetch-calendar-events/android/build.gradle" line="20" column="5"/> </issue> <issue id="GradleDynamicVersion" severity="Warning" message="Avoid using + in version numbers; can lead to unpredictable and unrepeatable builds (com.facebook.react:react-native:+)" category="Correctness" priority="4" summary="Gradle Dynamic Version" explanation="Using `+` in dependencies lets you automatically pick up the latest available version rather than a specific, named version. However, this is not recommended; your builds are not repeatable; you may have tested with a slightly different version than what the build server used. (Using a dynamic version as the major version number is more problematic than using it in the minor version position.)" errorLine1=" compile &apos;com.facebook.react:react-native:+&apos;" errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~" quickfix="studio"> <location file="/Users/develops/Projects/pwc/react-native-fetch-calendar-events/android/build.gradle" line="35" column="5"/> </issue> <issue id="Recycle" severity="Warning" message="This `Cursor` should be freed up after use with `#close()`" category="Performance" priority="7" summary="Missing `recycle()` calls" explanation="Many resources, such as TypedArrays, VelocityTrackers, etc., should be recycled (with a `recycle()` call) after use. This lint check looks for missing `recycle()` calls." errorLine1=" .query(" errorLine2=" ~~~~~"> <location file="/Users/develops/Projects/pwc/react-native-fetch-calendar-events/android/src/main/java/com/calendarevents/Utility.java" line="20" column="18"/> </issue> </issues>