Closed humanolaranja closed 11 months ago
Patch coverage has no change and project coverage change: -0.10%
:warning:
Comparison is base (
db563d2
) 92.38% compared to head (21ec352
) 92.28%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@humanolaranja Thanks for this PR. I appreciate the issue you are trying to solve, but I don't like the approach of adding a new static variable. In fact, those methods in ITunesResults should not be static anyway. I've made a change to address this and will push it into the next release. Thanks.
The problem: When using app flavors, you should have different app flavors with different app ids, so, maybe com.example.dev will be not available at the store, but com.example will. The problem is, when running com.example.dev, your log is flooded with this error, that is a valid error because the app id is not valid, but should not be displayed. I tried just init the upgrader if
kReleaseMode
, but this don't solve the issue, since the call is executed byUpgraderAlert
build.This PR will hide this logs the same way as in
play_store_search_api
anditunes_search_api:class ITunesSearchAPI