WAI
Status Update
Comments
jr...@google.com <jr...@google.com> #2
I see same issue and have been debugging it.
NOTE: It DOES NOT happen if not using support package, but use android level 14/15 library. I believe Honeycomb works well too.
My current workaround is to provide my own DialogFragment.show() method, like below:
public int show(FragmentTransaction transaction, String tag) {
return show(transaction, tag, false);
}
public int show(FragmentTransaction transaction, String tag, boolean allowStateLoss) {
transaction.add(this, tag);
mRemoved = false;
mBackStackId = allowStateLoss ? transaction.commitAllowingStateLoss() : transaction.commit();
return mBackStackId;
}
NOTE: It DOES NOT happen if not using support package, but use android level 14/15 library. I believe Honeycomb works well too.
My current workaround is to provide my own DialogFragment.show() method, like below:
public int show(FragmentTransaction transaction, String tag) {
return show(transaction, tag, false);
}
public int show(FragmentTransaction transaction, String tag, boolean allowStateLoss) {
transaction.add(this, tag);
mRemoved = false;
mBackStackId = allowStateLoss ? transaction.commitAllowingStateLoss() : transaction.commit();
return mBackStackId;
}
da...@arneclo.com <da...@arneclo.com> #4
But Google pls fix this issue, as the expected behaviors must be consistent with ICS DialogFragment + FragmentManager and support package DialogFragment + FragmentManager.
It happens with both Support Package v4 r6 and v13 r6.
It happens with both Support Package v4 r6 and v13 r6.
jr...@google.com <jr...@google.com> #5
I have this problem too.
As a workaround I use a boolean in the onActivityResult to mark the desired dialog and show the dialog in the onResume.
As a workaround I use a boolean in the onActivityResult to mark the desired dialog and show the dialog in the onResume.
Description
Does this feature request already exist in the tracker? No
Identify the developer feature most relevant to your feature request: Data API
Feature Request Description: We use the Google Analytics RunReport API to store analytics data. API Documentation URL :https://developers.google.com/analytics/devguides/reporting/data/v1/rest/v1beta/properties/runReport
Our current setup retrieves daily data from the API with 8 dimensions and 2 metrics, including date range and dimension filters (such as filtering by EventName).
However, we have noticed discrepancies between the EventCount reported in the Google Analytics Dashboard and the EventCount returned by the API for certain events. For example, on 24/11/2023, for the EventName "Session_Start":
EventCount in Google Analytics Dashboard: 109,262
EventCount in API Response: 61,526 This results in a discrepancy of about 47,000 missing events, suggesting data loss.
Upon contacting the Analytics team, we learned that the API response includes a "dataLossFromOtherRow" flag set to true, indicating data loss due to "Other Row" records.
The issue is that there is currently no way to retrieve these missing "Other Row" records.
What is an "Other Row"?
We propose either adding a flag in the API to allow retrieval of these missing records or providing a separate API to fetch them.
Impact of This Feature on Google Analytics Users: Implementing this feature would allow users to retrieve a complete set of data, including records lost due to the "Other Row" limitation, resulting in a more accurate and comprehensive data view.
Current Alternatives: At present, there is no method to fetch the missing records, leaving us with incomplete data from the API response, causing discrepancies in the EventCount.
If This Feature is Not Implemented, How Will You Address the Issue? We will continue with the current approach, accepting the missing data as part of the process."