`Day62` - Resolved the recyclerview issue ◦ So...

# 100daysofkotlin-2021

[JungIn Choi]

Day62
• Resolved the recyclerview issue
◦ Solution was rather easy. I set setOnScrollChangeListener to the NestedScrollView, instead of RecyclerView. Nice!
• Replaced some urls into in app urls
• Fixed bug with back button
◦ I was creating two activities. Thought I replaced it to action controller way, but I did not erase the previous one.
• Backend fixes synchronization
Day63
• Completed refund logic (backend handling + layout fixes)
◦ Hard part was updating user status (and corresponding layout) on pass refund.
◦ As user clicks refund button, I finished the PassDetailActivity and came back to MyPassFragment. However, user status did not change right away.
◦ First, I called the api inside onResume()
▪︎ However the status did not update rightaway. Plus, since onResume gets called whenever user clicks a fragment inside the tab layout, layout flickered.
◦ Solution: I figured out there was some method using setResult, onActivityResult
▪︎ I had to call startActivityForResult instead of startActivity, to use this way…
▪︎ Finally I was able to call api inside onActivityResult, inside the correct branch with corresponding requestCode and resultCode.
• Backend fixes synchronization, Handled branch condition when user refunds rightaway
Self-Comment
• Finding one solution leads to additional shovelings…
• I printed lots of logs today… while debugging refund logic. Activity lifecycle is really… interesting haha
• Remote working has pros and cons.
◦ I now concentrate well in my room, (nice habbit formed while I was in graduate school, damn), so concentration itself is not an issue.
◦ But I rather get exhausted faster..? Maybe I concentrated too much..?
◦ So it goes like : work warming up -> 11am standup meeting -> early brunch -> work -> burning -> exhausted by 6pm(much earlier) -> dinner -> work continue at night😂
◦ Hoo but I guess it’s better than my recent routines.. work -> come home -> scroll on smartphone searching for rents 😂
Goals Tomorrow
• Report issues to backend engineer, when he fixes, continue QA on those parts.
• Handle “user who never purchased a pass”