ohteepee ActiveParent must have a focusedChild

When i try to use Ohteepee i got error: ActiveParent must have a focusedChild Here is stacktrace: https://pastebin.com/raw/89AgAqkJ This crash is showed when i click on numpad keyboard

Apr 30 '24 05:04 KarolCieslar

Same error here... Any updates on this?

May 07 '24 02:05 Alexminator99

Hi, I will be looking into it today. Thanks for your feedbacks

May 07 '24 07:05 tarikyasar

Cannot replicate the issue. Can you provide more detail or use case scenario? @KarolCieslar @Alexminator99

May 07 '24 17:05 tarikyasar

Cannot replicate the issue. Can you provide more detail or use case scenario? @KarolCieslar @Alexminator99

Im using buildSrc with libs.toml for versioning. Also, im using composeBom in the latest version. I think that's where the issue is. Google may released an update to compose that is affecting the focus of the text fields IMO. Can you to create a project from scratch and use the last compose bom version? If you are using material do the same. If you still cannot replicate I will create a small repo with the exact configuration I have to see if the issue persists, and if so, you can easily check it. Let me know @tarikyasar

May 07 '24 17:05 Alexminator99

@tarikyasar can You look at this?

May 09 '24 10:05 KarolCieslar

@KarolCieslar Could not find a time to try yet, sorry. Feel free to try Alex's scenario.

May 10 '24 06:05 tarikyasar

Cannot replicate the issue. Can you provide more detail or use case scenario? @KarolCieslar @Alexminator99

Im using buildSrc with libs.toml for versioning. Also, im using composeBom in the latest version. I think that's where the issue is. Google may released an update to compose that is affecting the focus of the text fields IMO. Can you to create a project from scratch and use the last compose bom version? If you are using material do the same. If you still cannot replicate I will create a small repo with the exact configuration I have to see if the issue persists, and if so, you can easily check it. Let me know @tarikyasar

Could You make a repo for traikaysar?

May 10 '24 10:05 KarolCieslar

Same issue here i'm using

androidxComposeBom = "2024.05.00" material3 = "1.2.1" ohteepee = "1.0.7"

May 22 '24 10:05 OdeyFox

Cannot replicate the issue. Can you provide more detail or use case scenario? @KarolCieslar @Alexminator99

Im using buildSrc with libs.toml for versioning. Also, im using composeBom in the latest version. I think that's where the issue is. Google may released an update to compose that is affecting the focus of the text fields IMO. Can you to create a project from scratch and use the last compose bom version? If you are using material do the same. If you still cannot replicate I will create a small repo with the exact configuration I have to see if the issue persists, and if so, you can easily check it. Let me know @tarikyasar

Could You make a repo for traikaysar?

Sure let me get that going and by Friday I will have it.

May 23 '24 05:05 Alexminator99

Hi, I noticed the same issue in my project. In my setup I'm using the version catalog to define the Compose BOM. The cause for my issue was that I was using a alpha release of the compose Material3 library androidx.compose.material3:material3:1.4.0-alpha08, that internally used androidx.compose.ui:ui-android:1.7.0-alpha08.

I forked your project and did some testing. In the OhTeePeeCell composable function I changed the value used by the BasicTextField to a simple String and noticed that the crash was resolved. This lead me to the right track and I inspected how this case is handled internally in the BasicTextField composable. I copied the implementation from it to your OhTeePeeCell and now everything is working correctly. In my opinion there is a bug in the compose library but I can't be 100% sure.

I have created a PR https://github.com/composeuisuite/ohteepee/pull/27 from the fork so you can merge it if you approve the fix. If not just let me know and I will close it.

May 24 '24 13:05 brunoblazincdecode

@brunoblazincdecode Thank you for the PR Bruno. Sorry for the delay, it has been busy lately.

Jun 05 '24 13:06 tarikyasar

@Mat-Agh 👋

Jun 05 '24 13:06 tarikyasar

@Mat-Agh 👋

When is the closest time you guys can release a new version?

Jun 06 '24 07:06 Mat-Agh

@Mat-Agh There seems to be some problem with publishing via Jitpack caused by this fix. Will be working on it as soon as I can.

Jun 06 '24 09:06 tarikyasar

there is still a problem with the jitpack build.

Jun 06 '24 13:06 Mat-Agh

Any updates on this??

Jun 14 '24 17:06 Alexminator99

@Alexminator99 Yes, I finally found the time to fix the issue. You can go with the version 1.0.10, thanks for your patience.

Jun 15 '24 14:06 tarikyasar

This issues is fixed with 1.0.10

Jul 03 '24 15:07 ilyasipek

Thank you for your notification.

On Wed, Jul 3, 2024 at 6:47 PM ilyas ipek @.***> wrote:

This issues is fixed with 1.0.10

— Reply to this email directly, view it on GitHub https://github.com/composeuisuite/ohteepee/issues/22#issuecomment-2206510263, or unsubscribe https://github.com/notifications/unsubscribe-auth/A5A6HROTDZE7AFD47IUDPYLZKQI2BAVCNFSM6AAAAABG7SAWMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBWGUYTAMRWGM . You are receiving this because you were mentioned.Message ID: @.***>

Jul 04 '24 10:07 Mat-Agh