Skip to content

Android build error "Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type 'android.content.pm.ApplicationInfo?" with compileSdkVersion 35 #147

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
shuwenli-tomo opened this issue Mar 31, 2025 · 2 comments
Closed

Android build error "Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type 'android.content.pm.ApplicationInfo?" with compileSdkVersion 35 #147

shuwenli-tomo opened this issue Mar 31, 2025 · 2 comments

Comments

@shuwenli-tomo
Copy link

e: file:///Users/xxx/.pub-cache/hosted/pub.dev/segment_analytics-1.1.3/android/src/main/kotlin/com/segment/analytics/AnalyticsPlugin.kt:146:59 Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type 'android.content.pm.ApplicationInfo?'.

Reproduce:

  1. segment-analysis: 1.1.3
  2. upgrade compileSdkVersion 34 to 35
  3. build and run android

Possible reason:
In Kotlin 35, the PackageInfo.java mark ApplicationInfo with Nullable annotation.
neelkanth-kaushik added a commit that referenced this issue May 13, 2025
@neelkanth-kaushik
Patch for Github issue #147
6154cd5
@neelkanth-kaushik neelkanth-kaushik mentioned this issue May 13, 2025
Merged
neelkanth-kaushik added a commit that referenced this issue May 13, 2025
@neelkanth-kaushik
Patch for Github issue #147
74e54ac
@neelkanth-kaushik
Copy link
Contributor

Thanks for reporting the issue, we are working on it.

neelkanth-kaushik added a commit that referenced this issue May 13, 2025
@neelkanth-kaushik
Patch for Github issue #147
d4b25e8
neelkanth-kaushik added a commit that referenced this issue May 13, 2025
@neelkanth-kaushik
Patch for Github issue #147
01e3a28
MichaelGHSeg pushed a commit that referenced this issue May 20, 2025
@neelkanth-kaushik
Patches for Github Issues (#159)
6eb6f1f 
* Patch for Github Issue #144

* Patch for Github issue #147

* Patch for Github issue #147

* Patch for Github issue #144

* Patch for Github issue #147

* Patch for Github issue #147

* Patch for Github issue #138

* Patch for Github issue #138

* Patch for Github Issue #152

* Patch for Github Issue #152

* Testing patch for Github Issue #157

* Patch for Github Issue #157
MichaelGHSeg added a commit that referenced this issue May 20, 2025
@MichaelGHSeg @neelkanth-kaushik
Release/1.1.7 (#161)
1c6cd64 
* Patches for Github Issues (#159)

* Patch for Github Issue #144

* Patch for Github issue #147

* Patch for Github issue #147

* Patch for Github issue #144

* Patch for Github issue #147

* Patch for Github issue #147

* Patch for Github issue #138

* Patch for Github issue #138

* Patch for Github Issue #152

* Patch for Github Issue #152

* Testing patch for Github Issue #157

* Patch for Github Issue #157

* Updating for 1.1.7 release

* Removing unnecessary library name

---------

Co-authored-by: Neelkanth Kaushik <[email protected]>
@neelkanth-kaushik
Copy link
Contributor

Please update the library to version 1.1.7.

@t-unit t-unit mentioned this issue Nov 19, 2024
Open
This was referenced May 23, 2025
Closed
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@neelkanth-kaushik @shuwenli-tomo