When using suspend fun in Room Dao methods, following error: Not sure how to convert a Cursor to this method's return type (java.lang.Object). [236612358]

Fixed

Bug

Status Update

No update yet.

Description

ja...@gmail.com

created issue #1

Jun 21, 2022 05:30AM

Component used: Room with suspend functions i.e. coroutines

error: /Users/jayshah/AndroidStudioProjects/SampleMemoryNotes/app/build/tmp/kapt3/stubs/debug/com/example/samplememorynotes/framework/db/NoteDao.java:17: error: Not sure how to convert a Cursor to this method's return type (java.lang.Object). public abstract java.lang.Object getNoteEntity(long id, @org.jetbrains.annotations.NotNull()

Usage:

// NoteDao.kt
@Dao
interface NoteDao {

    @Insert(onConflict = REPLACE)
    suspend fun addNoteEntity(noteEntity: NoteEntity)

    @Query("select * from note where id=:id")
    suspend fun getNoteEntity(id: Long): NoteEntity

    @Query("select * from note")
    suspend fun getAllNoteEntities(): List<NoteEntity>

    @Delete
    suspend fun deleteNoteEntity(noteEntity: NoteEntity)
}

Version used:

ext.coroutines_version = "1.3.0"
ext.room_version = "2.4.2"

    implementation "org.jetbrains.kotlinx:kotlinx-coroutines-core:$coroutines_version"
    implementation "org.jetbrains.kotlinx:kotlinx-coroutines-android:$coroutines_version"

    implementation "androidx.room:room-runtime:$room_version"
    kapt "androidx.room:room-runtime:$room_version"

    implementation 'androidx.legacy:legacy-support-v4:1.0.0'
    kapt "androidx.room:room-compiler:$room_version"
    implementation "androidx.room:room-ktx:$room_version"
    implementation "androidx.room:room-coroutines:2.1.0-alpha04"

Devices/Android versions reproduced on: Android emulator

If this is a bug in the library, we would appreciate if you could attach:

Sample project to trigger the issue: https://github.com/chetnashah/roomerrornotes
A screenrecord or screenshots showing the issue (if UI related):

Screenshot 2022-06-21 at 10.52.36 AM.png

1.4 MB

View

Download

Comments

ja...@gmail.com <ja...@gmail.com> #2Jun 21, 2022 05:43AM

Information redacted by Android Beta Feedback.

de...@gmail.com <de...@gmail.com> #3Jun 21, 2022 12:48PM

Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

de...@gmail.com <de...@gmail.com> #4Jun 21, 2022 07:46PM

I also have the same issue. Calls are so unstable it's ridiculous. I have already reported a similar issue, but they can't figure anything out. I too have bug reports.

ho...@gmail.com <ho...@gmail.com> #5Jun 22, 2022 09:25AM

Having same issue with bluejay (pixel 6a)..frustrating to use basic need

da...@google.com <da...@google.com> #6Jun 22, 2022 03:15PM

Thank you for the report.

Please capture the bugreport by enabling modem logs.

[How to enable "Verbose Vendor Logging"]

Menu->settings->about phone -> build number -> keep click the "build number" till it shows "now you are a developer"

Go to Settings -> system -> developer options

Scroll down and find "USB debugging". Enable it "Enable Verbose Vendor Logging" Enable it too

Whenever issue observed, please do:

Settings -> System -> Developer Options -> Click "Bug report".

It will take few minutes to generate A bugreport. Please save and share it.

Note: Please upload the bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.

da...@google.com <da...@google.com> #7Jun 22, 2022 03:32PM

Called voicemail and the dropout happened within a few seconds of the call
starting. (At around 9:05 AEDST)

https://drive.google.com/drive/folders/1Hus4Btkjsi1wKimmI8GRp2CP7XJ8hvDf

On Mon, 22 July 2024, 8:52 am , <buganizer-system@google.com> wrote:

- Show quoted text -

yy...@gmail.com <yy...@gmail.com> #8Jun 23, 2022 01:43AM

Thank you for the update, we'll update this issue once more information becomes available.

ma...@gmail.com <ma...@gmail.com> #9Jun 26, 2022 12:16PM

I also have the same issue!

za...@gotocme.com <za...@gotocme.com> #10Jul 6, 2022 10:46AM

I have the same issue. Lost 6 calls this morning on a Pixel 6, Verizon network. Calls dropped after 30-45 seconds.

da...@google.com <da...@google.com> #11Jul 6, 2022 12:51PM

Me having the Same issue in Pixel 6 pro

si...@gmail.com <si...@gmail.com> #12Jul 8, 2022 06:11AM

same problem pixel 6

zs...@gmail.com <zs...@gmail.com> #13Jul 11, 2022 04:22PM

I have the same issue with my P6 Pro - update today every calls drops out after about 30 secs

da...@google.com <da...@google.com> #14Jul 11, 2022 05:17PM

I am having the same issue as well on my P6 Pro.

ge...@gmail.com <ge...@gmail.com> #15Jul 26, 2022 07:02AM

Same. Pixel 6. Toggling audio output to Speaker (or just waiting 10-20 seconds) temporarily resolves the issue, but the drop-outs continue to occur every minute or so.

da...@google.com <da...@google.com> Jul 26, 2022 12:50PM

Marked as fixed.

19...@gmail.com <19...@gmail.com> #16Oct 19, 2022 01:07AM

Pixel 6 here, turning on the speaker doesnt help. Connecting to a headset does. Its like its not happening.

pi...@gmail.com <pi...@gmail.com> #17Jul 7, 2023 11:06AM

I've noticed the calls seem to work fine through the watch. Any of the speakers on the phone randomly dropout. It happens with every phone call

te...@gmail.com <te...@gmail.com> #18Jul 11, 2023 11:29PM

The same problem is impossible to use calls. Google pixel 6a

da...@google.com <da...@google.com> #19Jul 12, 2023 01:26PM

same problem, AT&T Pixel 6 Pro, beta 15/4.

da...@google.com <da...@google.com> #20Jul 12, 2023 01:28PM

Same problem with Telenor, Pixel 6a, Android 15 beta 4

io...@gmail.com <io...@gmail.com> #21Jul 19, 2023 11:26AM

Same issue also being faced by me on my Pixel 6 Pro. Call goes SLIENT or dropped after some seconds. This happened to my every call.

ri...@gmail.com <ri...@gmail.com> #22Aug 4, 2023 05:04AM

Same issue on every call Pixel 6a

bl...@gmail.com <bl...@gmail.com> #23Aug 16, 2023 11:29AM

Comment has been deleted.

Message last modified on Aug 16, 2023 11:29AM

da...@davwheat.dev <da...@davwheat.dev> #24Aug 16, 2023 11:29AM

What

Feature request

New Bug report following another call drop

Where

Build and device data

- Build Number: google/bluejay_beta/bluejay:15/AP31.240617.009/12094726:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Google Play services
com.google.android.gms
Version 242632044 (24.26.32 (260400-650348549))
System App (Updated)

Android System WebView
com.google.android.webview
Version 647813433 (126.0.6478.134)
System App (Updated)

Network operator: Jio True5G
SIM operator: Jio

Filed by Android Beta Feedback. Version (Updated): 2.43-betterbug.external_20240710_RC01 (DOGFOOD)
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

ra...@gmail.com <ra...@gmail.com> #25Sep 5, 2023 03:11PM

Information redacted by Android Beta Feedback.

ma...@gmail.com <ma...@gmail.com> #26Sep 19, 2023 09:39AM

I don't think it's something to do with the network or region but a glitch in recent update.
I see this as S0 and P2. I believe this should be S0 and P0, as the basic purpose of a phone has gone for a toss.
Please resolve the issue ASAP

sh...@navi.com <sh...@navi.com> #27Oct 13, 2023 10:15AM

My workaround: I use an external wired headset: USB-C --> Audio jack --> wired headset

mr...@gmail.com <mr...@gmail.com> #28Jan 5, 2024 06:29AM

What

Feature request

Connecting to Bluetooth earbuds send to fix the problem.

Where

Build and device data

- Build Number: google/raven_beta/raven:15/AP31.240617.009/12094726:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Google Play services
com.google.android.gms
Version 242663044 (24.26.63 (260400-652952954))
System App (Updated)

Android System WebView
com.google.android.webview
Version 647813433 (126.0.6478.134)
System App (Updated)

Network operator: Verizon
SIM operator: Verizon

pa...@gmail.com <pa...@gmail.com> #29Feb 22, 2024 07:26PM

Is there any progress or update on this one? If this doesn't get resolved before the final release, it's going to be a bloodbath. I cannot overstate how upset I am that Google cannot even make phone calls reliable on a flagship series of phones

ah...@gmail.com <ah...@gmail.com> #30Sep 12, 2024 01:00PM

What

Feature request

Doesn't drop out with Bluetooth head phones or android auto and some times is fine with speakerphone

Where

Build and device data

Debugging information
Google Play services
com.google.android.gms
Version 242832044 (24.28.32 (260400-653762049))
System App (Updated)

Android System WebView
com.google.android.webview
Version 647813433 (126.0.6478.134)
System App (Updated)

Network operator: Spark NZ
SIM operator: Spark NZ

ni...@gmail.com <ni...@gmail.com> #31Dec 19, 2024 12:25PM

What

Feature request

Can someone please update me on the issue? This is rendering my phone useless for making phone calls.

Where

Build and device data

Debugging information
Google Play services
com.google.android.gms
Version 242663044 (24.26.63 (260400-652952954))
System App (Updated)

Android System WebView
com.google.android.webview
Version 647818633 (126.0.6478.186)
System App (Updated)

Network operator: Optus
SIM operator: Optus

co...@gmail.com <co...@gmail.com> #32Feb 11, 2025 05:24AM

It's been 5 days since this issue started to be widely reported, and yet no official update. I don't believe Google is treating this clearly widespread issue with the due care and attention it deserves. The #1 reason we have these devices is because they make calls. This functionality, the namesake of the device, is rendered useless right now. Its a CORE feature.

Google sitting on it's hands.

Issue 236612358

Description

Issue summary

Comments

ja...@gmail.com <ja...@gmail.com> #2Jun 21, 2022 05:43AM

de...@gmail.com <de...@gmail.com> #3Jun 21, 2022 12:48PM

de...@gmail.com <de...@gmail.com> #4Jun 21, 2022 07:46PM

ho...@gmail.com <ho...@gmail.com> #5Jun 22, 2022 09:25AM

da...@google.com <da...@google.com> #6Jun 22, 2022 03:15PM

da...@google.com <da...@google.com> #7Jun 22, 2022 03:32PM

yy...@gmail.com <yy...@gmail.com> #8Jun 23, 2022 01:43AM

ma...@gmail.com <ma...@gmail.com> #9Jun 26, 2022 12:16PM

za...@gotocme.com <za...@gotocme.com> #10Jul 6, 2022 10:46AM

da...@google.com <da...@google.com> #11Jul 6, 2022 12:51PM

si...@gmail.com <si...@gmail.com> #12Jul 8, 2022 06:11AM

zs...@gmail.com <zs...@gmail.com> #13Jul 11, 2022 04:22PM

da...@google.com <da...@google.com> #14Jul 11, 2022 05:17PM

ge...@gmail.com <ge...@gmail.com> #15Jul 26, 2022 07:02AM

da...@google.com <da...@google.com> Jul 26, 2022 12:50PM

19...@gmail.com <19...@gmail.com> #16Oct 19, 2022 01:07AM

pi...@gmail.com <pi...@gmail.com> #17Jul 7, 2023 11:06AM

te...@gmail.com <te...@gmail.com> #18Jul 11, 2023 11:29PM

da...@google.com <da...@google.com> #19Jul 12, 2023 01:26PM

da...@google.com <da...@google.com> #20Jul 12, 2023 01:28PM

io...@gmail.com <io...@gmail.com> #21Jul 19, 2023 11:26AM

ri...@gmail.com <ri...@gmail.com> #22Aug 4, 2023 05:04AM

bl...@gmail.com <bl...@gmail.com> #23Aug 16, 2023 11:29AM

da...@davwheat.dev <da...@davwheat.dev> #24Aug 16, 2023 11:29AM

What

Feature request

Where

Build and device data

ra...@gmail.com <ra...@gmail.com> #25Sep 5, 2023 03:11PM

ma...@gmail.com <ma...@gmail.com> #26Sep 19, 2023 09:39AM

sh...@navi.com <sh...@navi.com> #27Oct 13, 2023 10:15AM

mr...@gmail.com <mr...@gmail.com> #28Jan 5, 2024 06:29AM

What

Feature request

Where

Build and device data

pa...@gmail.com <pa...@gmail.com> #29Feb 22, 2024 07:26PM

ah...@gmail.com <ah...@gmail.com> #30Sep 12, 2024 01:00PM

What

Feature request

Where

Build and device data

ni...@gmail.com <ni...@gmail.com> #31Dec 19, 2024 12:25PM

What

Feature request

Where

Build and device data

co...@gmail.com <co...@gmail.com> #32Feb 11, 2025 05:24AM

Add comment

Issue metadata