kiteco / issue-tracker

User-reported issues for Kite
https://Kite.com
1.75k stars 136 forks source link

Kite doesn't start on MacOS 10.13.6 (High Sierra) #329

Open rhstanton opened 4 years ago

rhstanton commented 4 years ago

Required Information To help us triage your issue effectively, please make sure you've completed these steps before opening this issue. Issues with not enough information may be deprioritized or ignored.

When I visited kite://settings/logs to download my logs, an error window popped up telling me "Error trying to run Kite Copilot. We have to exit." It also told me to open an issue here (which I was already doing...). Here's the contents of my log file:

2020-08-06T19:31:41.333Z [copilot] error: unhandled error

Describe the bug A clear description of what the bug is. Include steps to reproduce the bug if necessary.

Kite does not start on my machine when I click on it. No Copilot window pops up, and there's no "Kite" process visible in the Activity monitor. It runs fine on two other machines running newer versions of MacOS.

Screenshots If applicable, add screenshots to help explain your problem.

Screen Shot 2020-08-06 at 12 35 36 PM

itsdhung commented 4 years ago

Can you share the contents of the log file located at ~/.kite/logs/client.log?

rhstanton commented 4 years ago

There’s no file client.log. All I see is copilot.log, which currently contains

2020-08-06T19:31:41.333Z [copilot] error: unhandled error 
2020-08-06T19:57:49.685Z [copilot] error: unhandled error 

On Aug 10, 2020, at 9:51 AM, Daniel Hung notifications@github.com wrote:

Can you share the contents of the log file located at ~/.kite/logs/client.log?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kiteco/issue-tracker/issues/329#issuecomment-671468215, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAQNZDXYCA4AY3DQRHM7VATSAAQSBANCNFSM4PW5DZMA.

itsdhung commented 4 years ago

Are you able to run Kite.app from your Applications folder? The client.log file should generated after you run it from there.

rhstanton commented 4 years ago

THat’s what I’ve been trying to do. I click on it as usual, but no Kite window pops up, no Kite process is visible in the Activity Monitor, and no client.log gets produced.

The only time I get further than this is when I try to gather information for the bug report by entering the URL kite://settings kite://settings in Chrome. Then this happens:

When I click “OK”, the error box disappears, and I get left here forever (still with no client.log file):

It never get beyond this point.

On Aug 10, 2020, at 10:51 AM, Daniel Hung notifications@github.com wrote:

Are you able to run Kite.app from your Applications folder? The client.log file should generated after you run it from there.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kiteco/issue-tracker/issues/329#issuecomment-671497348, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAQNZDV2CG23HYTRNKPMDTDSAAXQVANCNFSM4PW5DZMA.

rhstanton commented 4 years ago

I see the two screen clippings don't show up. Here they are:

1:

Screen Shot 2020-08-10 at 10 53 31 AM

2

Screen Shot 2020-08-10 at 10 55 06 AM

rhstanton commented 4 years ago

I do now see some output in the MacOS console. Maybe this will be helpful in tracking down the problem:

default 12:48:37.443675 -0700   launchservicesd CHECKIN:0x0-0x332332 83548 com.kite.Kite
default 12:48:37.912072 -0700   Kite    removed KiteHelper from launchd
default 12:48:37.913195 -0700   Kite    starting helper at: /Applications/Kite.app/Contents/Library/LoginItems/KiteHelper.app
default 12:48:38.440644 -0700   launchservicesd CHECKIN:0x0-0x333333 83551 com.kite.KiteHelper
default 12:48:38.491052 -0700   KiteHelper  starting from /Applications/Kite.app/Contents/Library/LoginItems/KiteHelper.app
default 12:48:38.515232 -0700   Kite    started: 1
default 12:48:38.579836 -0700   Kite    added KiteHelper to launchd
default 12:48:38.611529 -0700   KiteHelper  [Crashlytics] Version 3.7.1 (106)
default 12:48:38.805418 -0700   KiteHelper  Faulting in NSHTTPCookieStorage singleton
default 12:48:38.805446 -0700   KiteHelper  Faulting in CFHTTPCookieStorage singleton
default 12:48:38.805464 -0700   KiteHelper  Creating default cookie storage with process/bundle identifier
default 12:48:38.808026 -0700   KiteHelper  TIC Enabling TLS [1:0x62000016ac80]
default 12:48:38.808089 -0700   KiteHelper  TIC TCP Conn Start [1:0x62000016ac80]
default 12:48:38.808424 -0700   KiteHelper  Task <3CCEE2BD-445A-4213-BA08-82CA0D79DA99>.<1> setting up Connection 1
default 12:48:38.808455 -0700   KiteHelper  [1 <private> <private>] start
default 12:48:38.808661 -0700   KiteHelper  [Crashlytics:Crash:Reports] Packaged report with id '36db932017b7435f9a4de60fc587280c' for submission
default 12:48:38.812112 -0700   KiteHelper  background session setup waiting for reply: session <private> with identifier com.twitter.crashlytics.mac.crash.background-session
default 12:48:38.822971 -0700   KiteHelper  TIC TLS Event [1:0x62000016ac80]: 1, Pending(0)
default 12:48:38.846380 -0700   KiteHelper  TIC TLS Event [1:0x62000016ac80]: 2, Pending(0)
default 12:48:38.869362 -0700   KiteHelper  UNIX error exception: 17
default 12:48:38.874991 -0700   KiteHelper  UNIX error exception: 17
default 12:48:38.878914 -0700   KiteHelper  UNIX error exception: 17
default 12:48:38.882840 -0700   KiteHelper  TIC TLS Event [1:0x62000016ac80]: 11, Pending(0)
default 12:48:38.883823 -0700   KiteHelper  TIC TLS Event [1:0x62000016ac80]: 12, Pending(0)
default 12:48:38.884645 -0700   KiteHelper  TIC TLS Event [1:0x62000016ac80]: 14, Pending(0)
default 12:48:38.906032 -0700   KiteHelper  Task <12EEBCF2-57C5-4664-AF12-C9D58A53193A>.<5> is for <<private>>.<<private>>.<5>
default 12:48:38.906111 -0700   KiteHelper  background session setup reply received: session <private> with identifier com.twitter.crashlytics.mac.crash.background-session
default 12:48:38.912985 -0700   dasd    Submitted Activity: com.apple.CFNetwork-cc-527-74-Task <7FC836F7-1463-4C65-A4A3-29484631F02C>.<com.kite.KiteHelper>.<com.twitter.crashlytics.mac.crash.background-session>.<6>:AB10D0 <private>
default 12:48:38.913306 -0700   KiteHelper  System Trust Evaluation yielded status(0)
default 12:48:38.913950 -0700   KiteHelper  TIC TLS Trust Result [1:0x62000016ac80]: 0
default 12:48:38.919267 -0700   dasd    com.apple.CFNetwork-cc-527-74-Task <7FC836F7-1463-4C65-A4A3-29484631F02C>.<com.kite.KiteHelper>.<com.twitter.crashlytics.mac.crash.background-session>.<6>:AB10D0:[
    {name: ApplicationPolicy, policyWeight: 5.000, response: {Decision: Can Proceed, Score: 0.50}}
 ] sumScores:32.310000, denominator:34.910000, FinalDecision: Can Proceed FinalScore: 0.925523}
default 12:48:38.919337 -0700   dasd    'com.apple.CFNetwork-cc-527-74-Task <7FC836F7-1463-4C65-A4A3-29484631F02C>.<com.kite.KiteHelper>.<com.twitter.crashlytics.mac.crash.background-session>.<6>:AB10D0' CurrentScore: 0.925523, ThresholdScore: 0.490454 DecisionToRun:1
default 12:48:38.921756 -0700   KiteHelper  TIC TLS Event [1:0x62000016ac80]: 20, Pending(0)
default 12:48:38.921969 -0700   KiteHelper  TIC TCP Conn Connected [1:0x62000016ac80]: Err(16)
default 12:48:38.922278 -0700   KiteHelper  TIC TCP Conn Event [1:0x62000016ac80]: 1
default 12:48:38.922360 -0700   KiteHelper  TIC TCP Conn Event [1:0x62000016ac80]: 8
default 12:48:38.922492 -0700   KiteHelper  TIC TLS Handshake Complete [1:0x62000016ac80]
default 12:48:38.927025 -0700   KiteHelper  Task <3CCEE2BD-445A-4213-BA08-82CA0D79DA99>.<1> now using Connection 1
default 12:48:38.927130 -0700   KiteHelper  Task <3CCEE2BD-445A-4213-BA08-82CA0D79DA99>.<1> sent request, body N
default 12:48:38.936569 -0700   KiteHelper  checking for backup updates at https://release.kite.com/fallback/0.20200804.0/appcast.xml
default 12:48:38.936911 -0700   KiteHelper  checking for backup updates at https://release.kite.com/fallback/0.20200804.0/appcast.xml
default 12:48:38.944461 -0700   KiteHelper  TIC Enabling TLS [2:0x60400016b1c0]
default 12:48:38.944510 -0700   KiteHelper  TIC TCP Conn Start [2:0x60400016b1c0]
default 12:48:38.944629 -0700   KiteHelper  Task <A0008A81-07BE-47B9-961D-6DFECA7F1C3C>.<1> setting up Connection 2
default 12:48:38.944657 -0700   KiteHelper  [2 <private> <private>] start
default 12:48:38.960851 -0700   KiteHelper  TIC TLS Event [2:0x60400016b1c0]: 1, Pending(0)
default 12:48:38.968502 -0700   KiteHelper  TIC TLS Event [2:0x60400016b1c0]: 2, Pending(0)
default 12:48:38.968954 -0700   KiteHelper  TIC TLS Event [2:0x60400016b1c0]: 2, Pending(0)
default 12:48:38.970515 -0700   KiteHelper  TIC TLS Event [2:0x60400016b1c0]: 11, Pending(0)
default 12:48:38.971393 -0700   KiteHelper  TIC TLS Event [2:0x60400016b1c0]: 12, Pending(0)
default 12:48:38.972246 -0700   KiteHelper  TIC TLS Event [2:0x60400016b1c0]: 14, Pending(0)
default 12:48:38.981518 -0700   KiteHelper  System Trust Evaluation yielded status(0)
default 12:48:38.989484 -0700   KiteHelper  TIC TLS Trust Result [2:0x60400016b1c0]: 0
default 12:48:38.991808 -0700   KiteHelper  Task <3CCEE2BD-445A-4213-BA08-82CA0D79DA99>.<1> received response, status 200 content U
default 12:48:38.992018 -0700   KiteHelper  Task <3CCEE2BD-445A-4213-BA08-82CA0D79DA99>.<1> response ended
default 12:48:38.999167 -0700   KiteHelper  TIC TLS Event [2:0x60400016b1c0]: 20, Pending(0)
default 12:48:39.999678 -0700   KiteHelper  TIC TCP Conn Connected [2:0x60400016b1c0]: Err(16)
default 12:48:39.000344 -0700   KiteHelper  TIC TCP Conn Event [2:0x60400016b1c0]: 1
default 12:48:39.000473 -0700   KiteHelper  TIC TCP Conn Event [2:0x60400016b1c0]: 8
default 12:48:39.000599 -0700   KiteHelper  TIC TLS Handshake Complete [2:0x60400016b1c0]
default 12:48:39.002178 -0700   KiteHelper  Task <A0008A81-07BE-47B9-961D-6DFECA7F1C3C>.<1> now using Connection 2
default 12:48:39.002365 -0700   KiteHelper  Task <A0008A81-07BE-47B9-961D-6DFECA7F1C3C>.<1> sent request, body N
default 12:48:39.004649 -0700   KiteHelper  TIC TCP Conn Cancel [1:0x62000016ac80]
default 12:48:39.004866 -0700   KiteHelper  [1 <private> stream, pid: 83551, url: https://settings.crashlytics.com/spi/v2/platforms/mac/apps/com.kite.KiteHelper/settings?build_version=1&display_version=1.0&instan, tls] cancelled
    [1.1 20305198-5FAA-45EB-9457-265FA1AD95DE <private>.49858<-><private>]
    Connected Path: satisfied (Path is satisfied), interface: en0, ipv4, dns
    Duration: 0.196s, DNS @0.000s took 0.005s, TCP @0.008s took 0.004s, TLS took 0.100s
    bytes in/out: 5784/1248, packets in/out: 11/9, rtt: 0.003s, retransmitted packets: 0, out-of-order packets: 0
default 12:48:39.005256 -0700   KiteHelper  TIC TCP Conn Destroyed [1:0x62000016ac80]
error   12:48:39.006180 -0700   KiteHelper  TIC Read Status [1:0x0]: 1:57
error   12:48:39.006224 -0700   KiteHelper  TIC Read Status [1:0x0]: 1:57
default 12:48:39.007914 -0700   KiteHelper  Task <A0008A81-07BE-47B9-961D-6DFECA7F1C3C>.<1> received response, status 404 content K
default 12:48:39.008022 -0700   KiteHelper  Task <A0008A81-07BE-47B9-961D-6DFECA7F1C3C>.<1> response ended
error   12:48:39.074475 -0700   KiteHelper  Error: An error occurred in retrieving update information. Please try again later. An error occurred while parsing the update feed. (URL (null))
error   12:48:39.074526 -0700   KiteHelper  Error: An error occurred while parsing the update feed. (null) (URL (null))
error   12:48:39.074569 -0700   KiteHelper  Error: Line 1: Document is empty
 (null) (URL (null))
default 12:48:39.074664 -0700   KiteHelper  updater error: Error Domain=SUSparkleErrorDomain Code=1002 "An error occurred in retrieving update information. Please try again later." UserInfo={NSLocalizedFailureReason=An error occurred while parsing the update feed., NSLocalizedDescription=An error occurred in retrieving update information. Please try again later., NSUnderlyingError=0x60000004b3d0 {Error Domain=SUSparkleErrorDomain Code=1000 "An error occurred while parsing the update feed." UserInfo={NSLocalizedDescription=An error occurred while parsing the update feed., NSUnderlyingError=0x618000048dc0 {Error Domain=NSXMLParserErrorDomain Code=4 "Line 1: Document is empty
" UserInfo={NSLocalizedDescription=Line 1: Document is empty
}}}}}
default 12:48:39.075816 -0700   KiteHelper  terminating KiteHelper
default 12:48:41.100455 -0700   nsurlsessiond   [74 <private> stream, bundle id: com.kite.KiteHelper, pid: 527, url: https://reports.crashlytics.com/sdk-api/v1/platforms/mac/apps/com.kite.KiteHelper/reports, traffic class: 100, tls, indefinite] cancelled
    [74.1 E6F3EC33-17CE-4098-8AB3-B0F56774867C <private>.49859<-><private>]
    Connected Path: satisfied (Path is satisfied), interface: en0, ipv4, dns
    Duration: 2.179s, DNS @0.000s took 0.014s, TCP @0.015s took 0.062s, TLS took 0.153s
    bytes in/out: 4192/15023, packets in/out: 5/13, rtt: 0.062s, retransmitted packets: 0, out-of-order packets: 0
default 12:48:41.100780 -0700   dasd    COMPLETED com.apple.CFNetwork-cc-527-74-Task <7FC836F7-1463-4C65-A4A3-29484631F02C>.<com.kite.KiteHelper>.<com.twitter.crashlytics.mac.crash.background-session>.<6>:AB10D0 <private>!
default 12:48:41.100915 -0700   dasd    NO LONGER RUNNING com.apple.CFNetwork-cc-527-74-Task <7FC836F7-1463-4C65-A4A3-29484631F02C>.<com.kite.KiteHelper>.<com.twitter.crashlytics.mac.crash.background-session>.<6>:AB10D0 ...Tasks running in group [<private>] are 0!
iamrbtm commented 4 years ago

I have ths exact same issue... is there any solution to this? Screens are identical to the listed above...

sdsy888 commented 3 years ago

same problem here.

Mac M1, macOS Big Sur.

Fab4 commented 3 years ago

Hi,

Same probleme here on macOS Mojave version 10.14.6.

kkdima commented 3 years ago

Did anyone resolve this one? I can't launch the app on Big Sur 11.1

Screen Shot 2021-01-05 at 4 39 29 PM
collacocca commented 3 years ago

same here -

kite_issue

aimpsmile commented 3 years ago

same problem here.

macos 10.15.7 (19H15) MacBook Pro (13-inch, 2020, Two Thunderbolt 3 ports)

ghost commented 3 years ago

I have also the same problem in my "Mac mini (M1, 2020)"

therbta commented 3 years ago

Any solving?

zzainoo commented 3 years ago

same problem here.

Mac M1, macOS Big Sur.

same

antoineGit commented 3 years ago

Same

same problem here. Mac M1, macOS Big Sur.

same