search

chaitin / passionfruit

[WIP] Crappy iOS app analyzer
MIT License
1.66k stars 228 forks source link

Error while connecting or disconnecting USB after start passionfruit #80

Closed ViTokarev closed 3 years ago

ViTokarev commented 3 years ago

Windows 10 x64 Version 1809 (OS Build 17763.107):

npm  -v
6.14.9

node.exe -v
v14.15.2

frida.exe --version
14.1.3

iPhone SE 13.5.1 have Jail:

frida-server --version
2020-12-17 12:40:24.362 frida-server[2364:131176] === SSL Kill Switch 2: Preference set to 0.
2020-12-17 12:40:24.363 frida-server[2364:131176] === SSL Kill Switch 2: Substrate hook disabled.
12.10.4

Text error when I connect iPhone to PC:

listening on http://localhost:31337
  <-- GET /
  --> GET / 200 8ms 351b
  <-- GET /static/build.js
  --> GET /static/build.js 200 82ms 845.76kb
  <-- GET /static/0.build.js
  --> GET /static/0.build.js 200 9ms 61.58kb
  <-- GET /static/logo.svg?c7082950f991c849997b441024ae837c
  --> GET /static/logo.svg?c7082950f991c849997b441024ae837c 200 4ms 16.38kb
  <-- GET /apps/54f50b9f7e9859a19bd1555ffb731379f9155bfd
  --> GET /apps/54f50b9f7e9859a19bd1555ffb731379f9155bfd 200 2ms 351b
  <-- GET /static/build.js
  --> GET /static/build.js 200 76ms 845.76kb
  <-- GET /static/0.build.js
  --> GET /static/0.build.js 200 7ms 61.58kb
  <-- GET /static/logo.svg?c7082950f991c849997b441024ae837c
  --> GET /static/logo.svg?c7082950f991c849997b441024ae837c 200 4ms 16.38kb
  <-- GET /static/icon.svg

 Fatal error in , line 0
 Check failed: result.second.

FailureMessage Object: 000000B7145CDB90
 1: 00007FF656DD03DF napi_wrap+109311
 2: 00007FF656D04B7F std::basic_ostream<char,std::char_traits<char> >::operator<<+57151
 3: 00007FF65793D602 V8_Fatal+162
 4: 00007FF6573E14AD v8::internal::BackingStore::Reallocate+653
 5: 00007FF6576272E9 v8::ArrayBuffer::GetBackingStore+137
 6: 00007FF656C52EDD v8::internal::OrderedHashTable<v8::internal::OrderedHashMap,2>::NumberOfBucketsIndex+33677
 7: 00007FF656D9007C v8::internal::Malloced::operator delete+3196
 8: 00007FF6575ED92F v8::internal::Builtins::builtin_handle+321471
 9: 00007FF6575ECEC4 v8::internal::Builtins::builtin_handle+318804
10: 00007FF6575ED1B7 v8::internal::Builtins::builtin_handle+319559
11: 00007FF6575ED003 v8::internal::Builtins::builtin_handle+319123
12: 00007FF6576C919D v8::internal::SetupIsolateDelegate::SetupHeap+464173
13: 00007FF657661AA2 v8::internal::SetupIsolateDelegate::SetupHeap+40498
14: 00007FF657661AA2 v8::internal::SetupIsolateDelegate::SetupHeap+40498
15: 00007FF65765B6D9 v8::internal::SetupIsolateDelegate::SetupHeap+14953
16: 00007FF657661AA2 v8::internal::SetupIsolateDelegate::SetupHeap+40498
17: 00007FF657661AA2 v8::internal::SetupIsolateDelegate::SetupHeap+40498
18: 00007FF657661AA2 v8::internal::SetupIsolateDelegate::SetupHeap+40498
19: 00007FF657661AA2 v8::internal::SetupIsolateDelegate::SetupHeap+40498
20: 00007FF65765F75E v8::internal::SetupIsolateDelegate::SetupHeap+31470
21: 00007FF65765F34C v8::internal::SetupIsolateDelegate::SetupHeap+30428
22: 00007FF65752F831 v8::internal::Execution::CallWasm+1649
23: 00007FF65752F09F v8::internal::Execution::Call+191
24: 00007FF65761A9E7 v8::Function::Call+615
25: 00007FFDFB7D6127 g_win32_run_session_bus+216803
26: 00007FFDFB7DA5D7 g_win32_run_session_bus+234387
27: 00007FF6575ED92F v8::internal::Builtins::builtin_handle+321471
28: 00007FF6575ECEC4 v8::internal::Builtins::builtin_handle+318804
29: 00007FF6575EDEB6 v8::internal::Builtins::builtin_handle+322886
30: 00007FF65752F4FE v8::internal::Execution::CallWasm+830
31: 00007FF65752F09F v8::internal::Execution::Call+191
32: 00007FF65761A9E7 v8::Function::Call+615
33: 00007FF656DF444B node::CallbackScope::~CallbackScope+1659
34: 00007FF656DF48B1 node::MakeCallback+209
35: 00007FFDFB7DA71E g_win32_run_session_bus+234714
36: 00007FF656E2469B uv_async_send+331
37: 00007FF656E23E2C uv_loop_init+1292
38: 00007FF656E23FCA uv_run+202
39: 00007FF656D300A5 v8::internal::OrderedHashTable<v8::internal::OrderedHashSet,1>::NumberOfBucketsOffset+9365
40: 00007FF656DA3867 node::Start+311
41: 00007FF656C0686C RC4_options+339820
42: 00007FF657BA523C v8::internal::compiler::RepresentationChanger::Uint32OverflowOperatorFor+153532
43: 00007FFE6EDE7E94 BaseThreadInitThunk+20
44: 00007FFE6FA77AD1 RtlUserThreadStart+33
ViTokarev commented 3 years ago

Okay, I've updated Frida on my iPhone to 14.1.3. It turned out to get a list of applications on the phone. But there is still a problem with the sudden error. Maybe everything is okay and get this:

listening on http://localhost:31337
  <-- GET /
  --> GET / 200 4ms 351b
  <-- GET /static/build.js
  --> GET /static/build.js 200 77ms 845.76kb
  <-- GET /static/0.build.js
  --> GET /static/0.build.js 200 6ms 61.58kb
  <-- GET /static/logo.svg?c7082950f991c849997b441024ae837c
  --> GET /static/logo.svg?c7082950f991c849997b441024ae837c 200 3ms 16.38kb
An unhandledRejection occurred:
Rejection: Error: Unexpectedly timed out while waiting for app to launch
Error: Unexpectedly timed out while waiting for app to launch

#
# Fatal error in , line 0
# Check failed: result.second.
#
#
#
#FailureMessage Object: 000000E8813EE600
 1: 00007FF656DD03DF napi_wrap+109311
 2: 00007FF656D04B7F std::basic_ostream<char,std::char_traits<char> >::operator<<+57151
 3: 00007FF65793D602 V8_Fatal+162
 4: 00007FF6573E14AD v8::internal::BackingStore::Reallocate+653
 5: 00007FF6576272E9 v8::ArrayBuffer::GetBackingStore+137
 6: 00007FF656C52EDD v8::internal::OrderedHashTable<v8::internal::OrderedHashMap,2>::NumberOfBucketsIndex+33677
 7: 00007FF656D9007C v8::internal::Malloced::operator delete+3196
 8: 00007FF6575ED92F v8::internal::Builtins::builtin_handle+321471
 9: 00007FF6575ECEC4 v8::internal::Builtins::builtin_handle+318804
10: 00007FF6575ED1B7 v8::internal::Builtins::builtin_handle+319559
11: 00007FF6575ED003 v8::internal::Builtins::builtin_handle+319123
12: 00007FF6576C919D v8::internal::SetupIsolateDelegate::SetupHeap+464173
13: 00007FF657661AA2 v8::internal::SetupIsolateDelegate::SetupHeap+40498
14: 00007FF657661AA2 v8::internal::SetupIsolateDelegate::SetupHeap+40498
15: 00007FF65765B6D9 v8::internal::SetupIsolateDelegate::SetupHeap+14953
16: 00007FF657661AA2 v8::internal::SetupIsolateDelegate::SetupHeap+40498
17: 00007FF657661AA2 v8::internal::SetupIsolateDelegate::SetupHeap+40498
18: 00007FF65765B6D9 v8::internal::SetupIsolateDelegate::SetupHeap+14953
19: 00007FF6576E4CD2 v8::internal::SetupIsolateDelegate::SetupHeap+577634
20: 00007FF657661AA2 v8::internal::SetupIsolateDelegate::SetupHeap+40498
21: 00007FF65768E890 v8::internal::SetupIsolateDelegate::SetupHeap+224288
22: 00007FF65770AC8E v8::internal::SetupIsolateDelegate::SetupHeap+733214
23: 00007FF657681A0D v8::internal::SetupIsolateDelegate::SetupHeap+171421
24: 00007FF65765F64C v8::internal::SetupIsolateDelegate::SetupHeap+31196
25: 00007FF65752F8EF v8::internal::Execution::CallWasm+1839
26: 00007FF65752F9FB v8::internal::Execution::CallWasm+2107
27: 00007FF65753043A v8::internal::Execution::TryCall+378
28: 00007FF657510C55 v8::internal::MicrotaskQueue::RunMicrotasks+501
29: 00007FF6575109B0 v8::internal::MicrotaskQueue::PerformCheckpoint+32
30: 00007FF656DF4070 node::CallbackScope::~CallbackScope+672
31: 00007FF656DF446B node::CallbackScope::~CallbackScope+1691
32: 00007FF656DF48B1 node::MakeCallback+209
33: 00007FFE0333A71E g_win32_run_session_bus+234714
34: 00007FF656E2469B uv_async_send+331
35: 00007FF656E23E2C uv_loop_init+1292
36: 00007FF656E23FCA uv_run+202
37: 00007FF656D300A5 v8::internal::OrderedHashTable<v8::internal::OrderedHashSet,1>::NumberOfBucketsOffset+9365
38: 00007FF656DA3867 node::Start+311
39: 00007FF656C0686C RC4_options+339820
40: 00007FF657BA523C v8::internal::compiler::RepresentationChanger::Uint32OverflowOperatorFor+153532
41: 00007FFE6EDE7E94 BaseThreadInitThunk+20
42: 00007FFE6FA77AD1 RtlUserThreadStart+33
ViTokarev commented 3 years ago

So. Today I sat down to work and there are no more problems. It's strange. Whatever I do, now everything is in order, apparently after the OS reboot.

ChiChou commented 3 years ago

@ViTokarev this is a known issue. It happens randomly, and it is a bug in the native module. I totally have no idea on how to reproduce or fix it. Just restart the server when you see it

ChiChou commented 3 years ago

@ViTokarev Please downgrade to node.js v12. It seems to be a bug from nodejs v14