microg / microg/GmsCore

[ru.kykyryza] Can't load map

Open
#1,692 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

Affected app
Name: Связной Плюс
Package id: ru.kykyryza

Describe the bug
Can't load map of transaction location

To Reproduce
Steps to reproduce the behavior:

  1. Go to app
  2. Click on transaction in history
  3. Scroll down and tap to transaction location
  4. See error

Expected behavior
Endless load map

Screenshots
https://i.imgur.com/cdiPuqh.jpeg

System
Android Version: 11
Custom ROM: crDroid 7.4

microG
microG Core version: 0.2.23.214816
microG Self-Check results: All checks

Additional context

03-17 18:47:48.321 I/ActivityTaskManager(2792): START u0 {cmp=ru.kykyryza/ru.ftc.bender.ui.screen.timeline.details.ScreenTimelineDetailsActivity (has extras)} from uid 10307
03-17 18:47:48.325 I/android.hardware.power-service-qti(545): Power setMode: 5 to: 1
03-17 18:47:48.336 W/ActivityTaskManager(2792): Tried to set launchTime (0) < mLastActivityLaunchTime (49809206)
03-17 18:47:48.377 W/ru.kykyryza(31167): Accessing hidden field Landroid/widget/TextView;->mCursorDrawableRes:I (greylist-max-p, reflection, denied)
03-17 18:47:48.393 W/ru.kykyryza(31167): Accessing hidden field Landroid/widget/TextView;->mCursorDrawableRes:I (greylist-max-p, reflection, denied)
03-17 18:47:48.474 W/GeocodeFuser(4283): android.os.DeadObjectException
03-17 18:47:48.474 W/GeocodeFuser(4283): 	at android.os.BinderProxy.transactNative(Native Method)
03-17 18:47:48.474 W/GeocodeFuser(4283): 	at android.os.BinderProxy.transact(BinderProxy.java:550)
03-17 18:47:48.474 W/GeocodeFuser(4283): 	at org.microg.nlp.api.GeocoderBackend$Stub$Proxy.getFromLocationName(GeocoderBackend.java:310)
03-17 18:47:48.474 W/GeocodeFuser(4283): 	at org.microg.nlp.service.AsyncGeocoderBackend$getFromLocationNameSync$1.invoke(AsyncGeocoderBackend.kt:85)
03-17 18:47:48.474 W/GeocodeFuser(4283): 	at org.microg.nlp.service.AsyncGeocoderBackend$getFromLocationNameSync$1.invoke(AsyncGeocoderBackend.kt:84)
03-17 18:47:48.474 W/GeocodeFuser(4283): 	at org.microg.nlp.service.AsyncGeocoderBackend.executeWithTimeout$lambda-19(AsyncGeocoderBackend.kt:184)
03-17 18:47:48.474 W/GeocodeFuser(4283): 	at org.microg.nlp.service.AsyncGeocoderBackend.$r8$lambda$on3q61AhKsea80YBNYAVUTV1G_4(Unknown Source:0)
03-17 18:47:48.474 W/GeocodeFuser(4283): 	at org.microg.nlp.service.AsyncGeocoderBackend$$ExternalSyntheticLambda0.run(Unknown Source:8)
03-17 18:47:48.474 W/GeocodeFuser(4283): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
03-17 18:47:48.474 W/GeocodeFuser(4283): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
03-17 18:47:48.474 W/GeocodeFuser(4283): 	at java.lang.Thread.run(Thread.java:923)
03-17 18:47:48.479 W/GeocodeFuser(4283): android.os.DeadObjectException
03-17 18:47:48.479 W/GeocodeFuser(4283): 	at android.os.BinderProxy.transactNative(Native Method)
03-17 18:47:48.479 W/GeocodeFuser(4283): 	at android.os.BinderProxy.transact(BinderProxy.java:550)
03-17 18:47:48.479 W/GeocodeFuser(4283): 	at org.microg.nlp.api.GeocoderBackend$Stub$Proxy.getFromLocationName(GeocoderBackend.java:310)
03-17 18:47:48.479 W/GeocodeFuser(4283): 	at org.microg.nlp.service.AsyncGeocoderBackend$getFromLocationNameSync$1.invoke(AsyncGeocoderBackend.kt:85)
03-17 18:47:48.479 W/GeocodeFuser(4283): 	at org.microg.nlp.service.AsyncGeocoderBackend$getFromLocationNameSync$1.invoke(AsyncGeocoderBackend.kt:84)
03-17 18:47:48.479 W/GeocodeFuser(4283): 	at org.microg.nlp.service.AsyncGeocoderBackend.executeWithTimeout$lambda-19(AsyncGeocoderBackend.kt:184)
03-17 18:47:48.479 W/GeocodeFuser(4283): 	at org.microg.nlp.service.AsyncGeocoderBackend.$r8$lambda$on3q61AhKsea80YBNYAVUTV1G_4(Unknown Source:0)
03-17 18:47:48.479 W/GeocodeFuser(4283): 	at org.microg.nlp.service.AsyncGeocoderBackend$$ExternalSyntheticLambda0.run(Unknown Source:8)
03-17 18:47:48.479 W/GeocodeFuser(4283): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
03-17 18:47:48.479 W/GeocodeFuser(4283): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
03-17 18:47:48.479 W/GeocodeFuser(4283): 	at java.lang.Thread.run(Thread.java:923)
03-17 18:47:48.539 I/ActivityTaskManager(2792): Displayed ru.kykyryza/ru.ftc.bender.ui.screen.timeline.details.ScreenTimelineDetailsActivity: +217ms

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at ru.ftc.bender.ui.screen.timeline.details.ScreenTimelineDetailsActivity and trace the transaction-location map flow. Review the GeocoderBackend and AsyncGeocoderBackend stack entries, using the provided reproduction steps and DeadObjectException logs. Done means the transaction location map loads instead of remaining in an endless loading state.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java, kotlin
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.