User Profile

Hi guys,Ever since I upgraded to High Sierra my MPB 2016 denies to go to sleep after a period of inactivity. Display shuts off, but sleep doesn't come. If I command it to sleep or close the lid, it sleeps.After troubleshooting it for a day I narrowed the problem down to iOS simulator running (and not sure if it's its sharingd process, but it looks like it). Problem happens either or not I have iCloud enabled on the simulator device. Problem happens for both iPhone SE 10.3 and iPhone X 11.1 simulator. It doesn't matter if simulator executes some app or not. Just having the simulator running is causing the issue.Once I Quit the simulator, MPB goes to sleep after a period of inactivity as expected. When simulator runs, it shuts down the display, but vents keep working forever, no sleep.Any chance you can check/reply if this is not hapenning in your case on High Sierra? So I'd know if problem is localized to my MPB/environment.Regards,Stan.

I have a new warning per every target after upgrading to Xcode 11.4:Invalid debug info found, debug info will be strippedThis has never been the case for my code base before. Anything I can do to resolve these warning? Am I safe to release to the AppStore with these warnings? For one of the targets detailed info is:mismatched subprogram between llvm.dbg.label label and !dbg attachment call void @llvm.dbg.label(metadata !137) #2, !dbg !203 label %138 double (i8*)* @"\01__hidden#1918_" !137 = !DILabel(scope: !138, name: "zulu_time", file: !10, line: 196) !138 = distinct !DISubprogram(name: "parseTimezone", scope: !10, file: !10, line: 161, type: !139, scopeLine: 161, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !171, retainedNodes: !196) !203 = !DILocation(line: 196, column: 1, scope: !100, inlinedAt: !101) !100 = distinct !DISubprogram(name: "__hidden#1928_", scope: !10, file: !10, line: 161, type: !11, scopeLine: 161, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !6) mismatched subprogram between llvm.dbg.label label and !dbg attachment call void @llvm.dbg.label(metadata !347), !dbg !371 label %55 i32 (i8*, ...)* @"\01__hidden#1920_" !347 = !DILabel(scope: !348, name: "end_getDigits", file: !10, line: 140) !348 = distinct !DISubprogram(name: "getDigits", scope: !10, file: !10, line: 109, type: !349, scopeLine: 109, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !171, retainedNodes: !351) !371 = !DILocation(line: 140, column: 1, scope: !315) !315 = distinct !DISubprogram(name: "__hidden#1922_", scope: !10, file: !10, line: 109, type: !11, scopeLine: 109, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !6) DICompileUnit not listed in llvm.dbg.cu !171 = distinct !DICompileUnit(language: DW_LANG_C99, file: !7, producer: "Apple clang version 11.0.3 (clang-1103.0.32.29)", isOptimized: true, runtimeVersion: 0, emissionKind: FullDebug, enums: !12, retainedTypes: !172, imports: !180, nameTableKind: None) ld: warning: Invalid debug info found, debug info will be stripped !dbg attachment points at wrong subprogram for function !126 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, s: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !11) double (%0*, i8*, %0*, i32)* @"\01__hidden#2776_" br i1 %41, label %42, label %90, !dbg !152, !llvm.loop !155 !156 = !DILocation(line: 283, column: 3, scope: !157) !157 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !158) !157 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !158) ld: warning: Invalid debug info found, debug info will be stripped mismatched subprogram between llvm.dbg.label label and !dbg attachment

For two days in a row I can't access Ratings and Reviews section for my apps in the AppStore Connect. It only shows: We can't process your request. Go back to where you were and try again. If the problem continues, contact us. Is it only me?

iOS 14.0 MapKit stopped drawing MKPolyline for me when there is a custom MKTileOverlay below it. Everything works in MKMap without the MKTileOverlay, but as as soon as MKTileOverlay is added below everything (or everything is added on top of MKTileOverlay): MKCircle draws alright MKPolygon draws alright MKAnnotiation draws alright MKPolyline is not drawn The issue affects anything that is based on MKPolylineRenderer. Submitted to Apple as FB8751854. Does anyone know any trick for how to solve it? I tried on iOS 14.0.1 - same problem.

To resolve issues with Xcode 11.2 and UITextviews I recompiled under Xcode 11.1 (as I managed to have my Xcode 11.2 compiled app sumitted and approved just a day ago). Now the new build that I sent to AppStore connect is not even showing under the Activity>iOS Builds, even 30 minutes later.I tried another one, it went into the same black hole.Are Xcode 11.1 builds accepted? Is it a temporary hiccup on the AppStore Connect side? Statuses in Xcode 11.1 for these build are "Uploaded".Reference to Xcode 11.2 and UITextviews issues:https://forums.developer.apple.com/thread/125287

I can't find any categories, search is providing me with few 4 years old threads even if I know there are newer ones. No way to see threads I'm subscribed to or created myself. Or I'm missing some hidden buttons or the whole toolbar? Is anyone going to see this question? Heeeelp!

Starting from May 21st I'm getting reports from Russian users of my gps camera app that address field is not being populated in the app.When I test several Russian coordinates from these users, it all works alright for me sitting in Prague, Czech Republic - CLGeocoder reverseGeocodeLocation calls work alright for their coordinates.Same locations or any locations called via CLGeocoder reverseGeocodeLocation seem to be resulting in error for them at some stage when call is initiated from Russia.I believe that there is a goverment organization in Russia that might be blocking access for millions of IP addresses a day, in order to win over Telegram and anything else.I just wonder if anyone else is experiencing this issue with Russian users and reverse geocoding via CLGeocoder reverseGeocodeLocation.I've reported this issue to Apple as well.

I know there are guys here who are very good at interpreting Apple's English. Per Apple statement in AppStore connect:As a reminder, starting March 27, 2019 all new apps and app updates for iPhone or iPad, including universal apps, will need to be built with the iOS 12.1 SDK and support iPhone XS Max or the 12.9-inch iPad Pro (3rd generation). Screenshots for these devices will also be required. As of now, March 31st, 2019 I still see iPhone XS Max and iPad 3rd generation 12.9 screenshot as "Optional" in the AppStore connect.My apps are all built with iOS 12.1 and 12.2 now and I've been supporting X screens since long ago.My internal problem is that I don't like how XS Max screenshots are presented in the AppStore app. They are so small that users can hardly see anything. Screenshots for older screen sizes are more visible and I think that might be a reason for a lot of fellow devs not providing XS Max screenshots at all. Probably for games with having one landscape screenshot shown they are ok, but for the data intensive apps they are a disadvantage, imho. Is this "Optional" in XS Max and iPad 3rd gen 12.9 screenshots that is still in the AppStore Connect - is it a sign that some one at Apple just misinterpreted the submission requirement? I don't think screenshots were present in the original requirement from September 2018:Starting March 2019, all new apps and app updates for iPhone, including universal apps, will need to be built with the iOS 12 SDK and support iPhone XS Max. All new apps and app updates for Apple Watch will need to be built with the watchOS 5 SDK and supportApple Watch Series 4.Hope that someone can provide more insight or just thoughts on this.