google-developer-training / android-kotlin-fundamentals-apps

android-kotlin-fundamentals-apps
Other
1.68k stars 2.12k forks source link

Kotlin Android Fundamentals: Styles and themes - GDGFinderFinal app is crashing #574

Closed SudKul closed 3 years ago

SudKul commented 3 years ago

Name of the Codelab or Codelab URL Kotlin Android Fundamentals: Styles and themes

Describe the problem The GDGFinderFinal app is crashing when clicking on the FAB, generating the following exception:

E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.example.android.gdgfinder, PID: 21069
    retrofit2.HttpException: HTTP 404 Not Found
        at com.jakewharton.retrofit2.adapter.kotlin.coroutines.CoroutineCallAdapterFactory$BodyCallAdapter$adapt$2.onResponse(CoroutineCallAdapterFactory.kt:104)
        at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:129)
        at okhttp3.RealCall$AsyncCall.execute(RealCall.java:206)
        at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:923)
I/Process: Sending signal. PID: 21069 SIG: 9

Possible reason for crashing In the GdgApiService.kt file, the @GET("gdg-directory.json") is not getting resolved at the BASE_URL = "https://android-kotlin-fun-mars-server.appspot.com/".

In which lesson and step of the codelab can this issue be found? Lesson 10: Designing for everyone + Step 7. Solution code

How to reproduce? Run the GDGFinderFinal app, and click either on the FAB or the Menu --> GDG Search. It will momentarily show a new screen saying "Waiting for location and network result", and then crashes.

Versions

  1. Android Studio 4.0.1
  2. API 30

Additional information NIL

codelab: android-kotlin-fundamentals

@jtavva Can you look into this? Thanks in advance.

android-dev-lxl commented 3 years ago

@SudKul Thank you for reaching out to us. This should be fixed now.

Note: Please create a new emulator when you are testing this issue.

SudKul commented 3 years ago

Thank you @jtavva for such a quick turnaround. I appreciate your efforts.