You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the static analyzer, two errors show up:
Pods/ChimpKit/ChimpKit3/Helper Objects/CKSubscribeAlertView.m:103:20: Value stored to 'responseString' during its initialization is never read
Pods/ChimpKit/ChimpKit3/Helper Objects/CKAuthViewController.m:243:14: Value stored to 'responseString' during its initialization is never read
Consider moving the NSLog inside the "if (kCKDebug)" in the following code: (same issue in both places)
Many projects strive to build with zero warnings, including the static analyzer. This should be a quick fix and will make it easier for developers to maintain "zero warning" build policies.
When running the static analyzer, two errors show up:
Pods/ChimpKit/ChimpKit3/Helper Objects/CKSubscribeAlertView.m:103:20: Value stored to 'responseString' during its initialization is never read
Pods/ChimpKit/ChimpKit3/Helper Objects/CKAuthViewController.m:243:14: Value stored to 'responseString' during its initialization is never read
Consider moving the NSLog inside the "if (kCKDebug)" in the following code: (same issue in both places)
NSString *responseString = [[NSString alloc] initWithData:data encoding:NSUTF8StringEncoding];
if (kCKDebug) NSLog(@"Response String: %@", responseString);
Many projects strive to build with zero warnings, including the static analyzer. This should be a quick fix and will make it easier for developers to maintain "zero warning" build policies.