Commits
Michael Haney authored and GitHub committed a00703a5434
Completely reimplement storage in GDT (#5877) * Revert "Revert GDTCORStorage changes for now (#5778)" This reverts commit 93eb6d8c48a91c79d1329affd41b3e7260617ce4. * Store events and implement unit tests (#5790) Resolves many TODOs in the flat file storage system Bug fixes found by unit tests are also included. * Get rid of event iterators and add separate folders for batching (#5829) * Store events and implement unit tests (#5790) Resolves many TODOs in the flat file storage system Bug fixes found by unit tests are also included. * Change to explicit nil comparison * Address test comments - Makes all APIs async - Add thread-safety test - Comments on where files are stored - Broke up the library data get/set API into two blocks * Implement events and batch expirations (#5842) The upload coordinator will signal an expiration check whenever the app foregrounds. * Remove prioritizers, upload packages, data futures, and backwards compatibility (#5874) * Remove prioritizers, upload packages, data futures, and backwards compatibility * Update a comment and console logging * Reset the storage for every unit test, move event generation out of core init * Return a nil request if data is nil. * Fix prioritizer reference in watchOS test app * Remove unnecessary check for termination * Give more leeway for eventID generation Change the transport API to a GDTCORTarget Don't continue a long test after a failure * Return nil if an eventID couldn't be created Fix some swift in the watchOS test app * Fix all rawValue GDTCORTarget usage * Update CHANGELOGs * Remove initializer annotations (#5878) * Remove initializer designation from GDTCOREvent Change the target property to the target type * Add a couple more types * Make implicit retain explicit Nothing I do seems to get this warning to trigger locally... * Address loss of precision issue * Re-enable a disabled test Don't delete while enumerating * Additional test tweaks and hasEvents is now on the queue and async * Adjust GDTCCT to the new API * Always attempt to create a path, get rid of implicit self refs * Change all waiting for be DISPATCH_TIME_FOREVER for debugging purposes I suspect the travis machines are just overwhelmed, since the test errors don't make any sense. * Try using a different separator * Enable debug logging * Enable verbose pod lib lint output * Handle cases where the mappingID contains path components * Revert "Enable debug logging" This reverts commit b3e4a6ecc59b114e4960bcdb471605a105ddffb2. * Revert "Enable verbose pod lib lint output" This reverts commit a5b54460f90be6d21f2b3acab7beb55195b2ff24. * Revert "Change all waiting for be DISPATCH_TIME_FOREVER for debugging purposes" This reverts commit 55e4fff5dce444b595f48d29fef79dc8e96187ea. * Attempt to create a folder before writing * Temporarily enable verbose pod lib lint, again * Temporarily add debug logging back in * Don't double store events Also print out errors if there are any * Remove debug logging * Put debug logs back in for Crashlytics test * Update mock APIs to match and use a real target * remove debug logging * Apply nullability specifiers to Crashlytics mock class