Element could not be tapped issue

[odqwis]

Hi!

Have been using Appium for a while now, using cucumber on top having features, step definitions etc. Recently I got my machine updated and the OS version reinstalled (to support iOS 8). So I cloned the project, installed and updated all the gems and everything, everything is working ok apart from tapping in buttons (which is quite important...) - and it is still works with my previous machine...

So, with a break point, I tried to find the element using the name > find_element(:name, "button menu")

Looks like it finds it, returning #<Selenium::WebDriver::Element:0x..fab18cb766045e49c id="0">

But when I try to tap it it just fails...

find_element(:name, "button menu").click

Selenium::WebDriver::Error::UnknownError: elementId 1 could not be tapped

from /Users/user/.rvm/gems/ruby-2.0.0-p481/gems/selenium-webdriver-2.42.0/lib/selenium/webdriver/remote/response.rb:51:in `assert_ok'

Any idea why is this happening?

If I try using xpath (button("button menu").click) works just perfect...

Any idea why? This is not happening for all the buttons in the screen, I have a similar button right after it, same class etc, and it works as usual.

Thank you very much for your help.

Config:

appium_lib (4.1.0)

selenium-webdriver (2.42.0)

ruby 2.1.2p95

[Isaac Murchie]

What is in the Server logs?

--
http://appium.io
---
You received this message because you are subscribed to the Google Groups "Appium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to appium-discus...@googlegroups.com.
Visit this group at http://groups.google.com/group/appium-discuss.
For more options, visit https://groups.google.com/d/optout.

[odqwis]

Hi Isaac!

So the server logs, when I try to click the button, are:

info: --> POST /wd/hub/session/20b494bc-9056-4de3-947a-527fcafaa45c/element {"using":"name","value":"button menu"}

debug: Pushing command to appium work queue: "au.getElementByName('button menu')"

debug: Sending command to instruments: au.getElementByName('button menu')

debug: Sending command to instruments: au.getElementByName('button menu')

debug: [INST] 2014-08-20 23:28:35 +0000 Debug: Got new command 3 from instruments: au.getElementByName('button menu')

       

debug: [INST] 2014-08-20 23:28:35 +0000 Debug: evaluating au.getElementByName('button menu')

       

debug: [INST] 2014-08-20 23:28:35 +0000 Debug: evaluation finished

       

debug: [INST] 2014-08-20 23:28:35 +0000 Debug: Lookup returned [object UIAButton] with the name "button menu" (id: 1).

       

debug: [INST] 2014-08-20 23:28:35 +0000 Debug: responding with:

       

debug: [INST] 2014-08-20 23:28:35 +0000 Debug: Running system command #4: /usr/local/Cellar/node/0.10.30/bin/node /usr/local/lib/node_modules/a

ppium/node_modules/appium-uiauto/bin/command-proxy-client.js /tmp/instruments_sock 2,{"status":0,"value":{"ELEMENT":"1"}}...

       

debug: Socket data received (38 bytes)

debug: Socket data being routed.

debug: Got result from instruments: {"status":0,"value":{"ELEMENT":"1"}}

debug: Responding to client with success: {"status":0,"value":{"ELEMENT":"1"},"sessionId":"20b494bc-9056-4de3-947a-527fcafaa45c"}

info: <-- POST /wd/hub/session/20b494bc-9056-4de3-947a-527fcafaa45c/element 200 124.164 ms - 87 {"status":0,"value":{"ELEMENT":"1"},"sessionId"

:"20b494bc-9056-4de3-947a-527fcafaa45c"}

info: --> POST /wd/hub/session/20b494bc-9056-4de3-947a-527fcafaa45c/element/1/click {}

debug: Pushing command to appium work queue: "au.tapById('1')"

debug: Sending command to instruments: au.tapById('1')

debug: Sending command to instruments: au.tapById('1')

debug: [INST] 2014-08-20 23:28:35 +0000 Debug: Got new command 4 from instruments: au.tapById('1')

       

debug: [INST] 2014-08-20 23:28:35 +0000 Debug: evaluating au.tapById('1')

       

debug: [INST STDERR] 2014-08-21 00:28:35.398 ScriptAgent[7857:2f07] Log written to /Users/jp.nogueira/Library/Application Support/iPhone Simula

tor/7.1-64/Library/Logs/CrashReporter/UIALogs/ScriptError-2014-08-21-002835.plist

debug: [INST] 2014-08-20 23:28:35 +0000 Debug: UIAButton.tap()

       

debug: [INST] 2014-08-20 23:28:35 +0000 Debug: UIAButton could not be tapped

       

debug: [INST STDERR] 2014-08-21 00:28:35.506 ScriptAgent[7857:2f07] Log written to /Users/jp.nogueira/Library/Application Support/iPhone Simula

tor/7.1-64/Library/Logs/CrashReporter/UIALogs/ScriptError-2014-08-21-002835.plist

debug: Socket data received (57 bytes)

debug: Socket data being routed.

debug: Got result from instruments: {"status":13,"value":"elementId 1 could not be tapped"}

debug: Responding to client with error: {"status":13,"value":{"message":"An unknown server-side error occurred while processing the command.","

origValue":"elementId 1 could not be tapped"},"sessionId":"20b494bc-9056-4de3-947a-527fcafaa45c"}

info: <-- POST /wd/hub/session/20b494bc-9056-4de3-947a-527fcafaa45c/element/1/click 500 380.243 ms - 200 

debug: [INST] 2014-08-20 23:28:35 +0000 Error: VerboseError: elementId 1 could not be tapped

       

debug: [INST] 2014-08-20 23:28:35 +0000 Error: Error during eval: tapById@file:///usr/local/lib/node_modules/appium/6AE15253-08FA-4CEC-BD4A-D2A

0BA2A8E51/gesture-ext.js:23:25

       eval code

eval@[native code]

startProcessing@file:///usr/local/lib/node_modules/appium/FA82AEC7-9801-4AD1-B14E-E475CFCB6C41/commands.js:186:30

bootstrap@file:///usr/local/lib/node_modules/appium/13B23ED6-4672-472E-822D-E8DB65A04A99/bootstrap.js:18:29

global code@file:///usr/local/lib/node_modules/appium/AED59423-7DC6-46BA-A5DF-CCAB0C0F29AE/bootstrap-cc21e4c483e821ef.js:9:10

debug: [INST] 2014-08-20 23:28:35 +0000 Debug: responding with:

       

debug: [INST] 2014-08-20 23:28:35 +0000 Debug: Running system command #5: /usr/local/Cellar/node/0.10.30/bin/node /usr/local/lib/node_modules/a

ppium/node_modules/appium-uiauto/bin/command-proxy-client.js /tmp/instruments_sock 2,{"status":13,"value":"elementId 1 could not be tapped"}...

(it actually finishes with the ...)

Any idea?

Thanks a lot!

[odqwis]

Just another bit of information:

The new machine came with xCode 5.1.1 and the other one (the working one) is running 5.1, so I just installed the xCode 5.1, tried again, and fails as well. I ran out of idea...

[Isaac Murchie]

This is something weird going on with Instruments. Are you sure the element is the one you want? That it is clickable? 

On Thu, Aug 21, 2014 at 5:27 AM, odqwis <joaopala...@gmail.com> wrote:

Just another bit of information:

The new machine came with xCode 5.1.1 and the other one (the working one) is running 5.1, so I just installed the xCode 5.1, tried again, and fails as well. I ran out of idea...

--

[odqwis]

I think so Isaac, I can tap it manually and there is no really other status for that element, it is always there in the same position all the time.

I found it weird as well that find_element(:name, "button menu").click fails but button("button menu").click works fine!

I was testing on the simulator, but meanwhile I wanted to confirm that with a real device, and apparently in real device I can't event "find" the button (like it fails when I do find_element(:name, "button menu")).

You mentioned that the problem is with the instruments... Isn't instruments shared between all xCode versions? I have xCode 5.1.1 (latests stable version) installed and used as default, installed xCode 6 beta (for iOS 8) and installed xCode 5.1. just to try to run Appium with that (because the other machine has xCode 5.1). Can that be the reason for instruments to fail? I tried with xCode 5.1 and 5.1.1 and both version have the same issue to click the menu button.

Thanks a lot!

[NMKP]

I too facing the same issue. I am able to find the element and tap on it by using Appium inspector. When I tried with selenium webdriver it's not working.

[odqwis]

Hi NMKP!

What is your OS version? That' the only difference I can think of between this two version I am using.

With the recent appium update I was hopping that 1.2.2 fixed the problem but unfortunatly it is not the case.

Thanks!

[odqwis]

Sorry, all my fault!

I was checking the Appium version in the app for the old machine, and that matched my new machine version, but obviously the server is not updating as the app is updated, and I was still in appium 1.1.0... Downgraded the server to 1.1 and it is working fine.

So this is a bug with version 1.2.1 and 1.2.2 - tried with both versions - creating an issue.

[NMKP]

Hi Odqwis,

Thanks for your reply. I have downgraded the appium to 1.1.0. But I am still facing the issue.

Here is the appium server error:

info: Responding to client with error: {"status":13,"value":{"message":"An unknown server-side error occurred while processing the command.","origValue":"elementId 2 could not be tapped"},"sessionId":"ae64334e-14af-4013-b4bf-adf6bfad8e38"}

Thanks!

[odqwis]

Are you using simulator or a real device?

[NMKP]

Both I have tried. Issue remains the same.

[odqwis]

What kind of element are you trying to tap?

Just reallized it is failing for some items as well even using 1.1 - some work with 1.2.2, some with 1.1.1, some dont work with bot...

We should be doing something wrong, it is impossible that other people have the same issues, this would block them...

Anyone else has an idea?

Thanks.

[odqwis]

Back to version 1.2.2.

I am trying to access a button using find_element(:name, "button menu") and it works fine, but when I try to click it just fails - it works fine with button("button menu"), bot for some buttons I really need the find_elements...

So, for the button("button menu") I am getting this logs (no problem here):

info: [debug] Pushing command to appium work queue: "au.getElementByIndexPath('/0/0/3/4')"
info: [debug] Sending command to instruments: au.getElementByIndexPath('/0/0/3/4')
info: [debug] Sending command to instruments: au.getElementByIndexPath('/0/0/3/4')
info: [debug] [INST] 2014-08-27 13:19:16 +0000 Debug: Got new command 111 from instruments: au.getElementByIndexPath('/0/0/3/4')
      
info: [debug] [INST] 2014-08-27 13:19:16 +0000 Debug: evaluating au.getElementByIndexPath('/0/0/3/4')
      
info: [debug] [INST] 2014-08-27 13:19:16 +0000 Debug: evaluation finished
      
info: [debug] [INST] 2014-08-27 13:19:16 +0000 Debug: Lookup returned [object UIAButton] with the name "button menu" (id: 31).
      
info: [debug] Socket data received (39 bytes)
info: [debug] Socket data being routed.
info: [debug] Got result from instruments: {"status":0,"value":{"ELEMENT":"31"}}
info: [debug] Responding to client with success: {"status":0,"value":{"ELEMENT":"31"},"sessionId":"7f5c7061-48c8-4a7f-b9cc-85c9890f5ab2"}
info: <-- POST /wd/hub/session/7f5c7061-48c8-4a7f-b9cc-85c9890f5ab2/element 200 486.351 ms - 88 {"status":0,"value":{"ELEMENT":"31"},"sessionId":"7f5c7061-48c8-4a7f-b9cc-85c9890f5ab2"}
info: --> POST /wd/hub/session/7f5c7061-48c8-4a7f-b9cc-85c9890f5ab2/element/31/click {}
info: [debug] Pushing command to appium work queue: "au.tapById('31')"
info: [debug] Sending command to instruments: au.tapById('31')
info: [debug] Sending command to instruments: au.tapById('31')
info: [debug] [INST STDERR] 2014-08-27 14:19:16.194 ScriptAgent[48146:3007] Log written to /Users/jp.nogueira/Library/Application Support/iPhone Simulator/7.1-64/Library/Logs/CrashReporter/UIALogs/Scri
ptError-2014-08-27-141916.plist

info: [debug] [INST] 2014-08-27 13:19:16 +0000 Debug: responding with:
      
info: [debug] [INST] 2014-08-27 13:19:16 +0000 Debug: Running system command #112: /usr/local/Cellar/node/0.10.30/bin/node /Users/jp.nogueira/Documents/Automation/appium/node_modules/appium-uiauto/bin/
command-proxy-client.js /tmp/instruments_sock 2,{"status":0,"value":{"ELEMENT":"31"}}...
      
info: [debug] [INST] 2014-08-27 13:19:16 +0000 Debug: Got new command 112 from instruments: au.tapById('31')
      
info: [debug] [INST] 2014-08-27 13:19:16 +0000 Debug: evaluating au.tapById('31')
      
info: [debug] [INST] 2014-08-27 13:19:16 +0000 Debug: target.frontMostApp().elements()[0].elements()[3].elements()[4].tap()
      
info: [debug] [INST] 2014-08-27 13:19:16 +0000 Debug: evaluation finished
      
info: [debug] [INST] 2014-08-27 13:19:16 +0000 Debug: responding with:
      
info: [debug] [INST] 2014-08-27 13:19:16 +0000 Debug: Running system command #113: /usr/local/Cellar/node/0.10.30/bin/node /Users/jp.nogueira/Documents/Automation/appium/node_modules/appium-uiauto/bin/
command-proxy-client.js /tmp/instruments_sock 2,{"status":0,"value":""}...
      
info: [debug] Socket data received (25 bytes)
info: [debug] Socket data being routed.
info: [debug] Got result from instruments: {"status":0,"value":""}
info: [debug] Responding to client with success: {"status":0,"value":"","sessionId":"7f5c7061-48c8-4a7f-b9cc-85c9890f5ab2"}
info: <-- POST /wd/hub/session/7f5c7061-48c8-4a7f-b9cc-85c9890f5ab2/element/31/click 200 264.481 ms - 74 {"status":0,"value":"","sessionId":"7f5c7061-48c8-4a7f-b9cc-85c9890f5ab2"}

When I try the same exact thing but using find_element(:name, "button menu") it fails with Selenium::WebDriver::Error::UnknownError: elementId 32 could not be tapped from /Users/jp.nogueira/.rvm/gems/ruby-2.1.2/gems/selenium-webdriver-2.42.0/lib/selenium/webdriver/remote/response.rb:51:in `assert_ok'

info: --> POST /wd/hub/session/7f5c7061-48c8-4a7f-b9cc-85c9890f5ab2/element {"using":"id","value":"button menu"}
info: [debug] Pushing command to appium work queue: "au.getElementByAccessibilityId('button menu')"
info: [debug] Sending command to instruments: au.getElementByAccessibilityId('button menu')
info: [debug] Sending command to instruments: au.getElementByAccessibilityId('button menu')
info: [debug] [INST] 2014-08-27 13:23:16 +0000 Debug: Got new command 113 from instruments: au.getElementByAccessibilityId('button menu')
      
info: [debug] [INST] 2014-08-27 13:23:16 +0000 Debug: evaluating au.getElementByAccessibilityId('button menu')
      
info: [debug] [INST] 2014-08-27 13:23:16 +0000 Debug: evaluation finished
      
info: [debug] [INST] 2014-08-27 13:23:16 +0000 Debug: Lookup returned [object UIAButton] with the name "button menu" (id: 32).
      
info: [debug] Socket data received (39 bytes)
info: [debug] Socket data being routed.
info: [debug] Got result from instruments: {"status":0,"value":{"ELEMENT":"32"}}
info: [debug] Responding to client with success: {"status":0,"value":{"ELEMENT":"32"},"sessionId":"7f5c7061-48c8-4a7f-b9cc-85c9890f5ab2"}
info: <-- POST /wd/hub/session/7f5c7061-48c8-4a7f-b9cc-85c9890f5ab2/element 200 122.719 ms - 88 {"status":0,"value":{"ELEMENT":"32"},"sessionId":"7f5c7061-48c8-4a7f-b9cc-85c9890f5ab2"}
info: --> POST /wd/hub/session/7f5c7061-48c8-4a7f-b9cc-85c9890f5ab2/element/32/click {}
info: [debug] Pushing command to appium work queue: "au.tapById('32')"
info: [debug] Sending command to instruments: au.tapById('32')
info: [debug] Sending command to instruments: au.tapById('32')
info: [debug] [INST STDERR] 2014-08-27 14:23:17.003 ScriptAgent[48146:3007] Log written to /Users/jp.nogueira/Library/Application Support/iPhone Simulator/7.1-64/Library/Logs/CrashReporter/UIALogs/Scri
ptError-2014-08-27-142317.plist

info: [debug] [INST] 2014-08-27 13:23:16 +0000 Debug: responding with:
      
info: [debug] [INST] 2014-08-27 13:23:16 +0000 Debug: Running system command #114: /usr/local/Cellar/node/0.10.30/bin/node /Users/jp.nogueira/Documents/Automation/appium/node_modules/appium-uiauto/bin/
command-proxy-client.js /tmp/instruments_sock 2,{"status":0,"value":{"ELEMENT":"32"}}...
      
info: [debug] [INST] 2014-08-27 13:23:17 +0000 Debug: Got new command 114 from instruments: au.tapById('32')
      
info: [debug] [INST] 2014-08-27 13:23:17 +0000 Debug: evaluating au.tapById('32')
      
info: [debug] [INST] 2014-08-27 13:23:17 +0000 Debug: UIAButton.tap()
      
info: [debug] [INST STDERR] 2014-08-27 14:23:17.108 ScriptAgent[48146:3007] Log written to /Users/jp.nogueira/Library/Application Support/iPhone Simulator/7.1-64/Library/Logs/CrashReporter/UIALogs/Scri
ptError-2014-08-27-142317.plist

info: [debug] [INST] 2014-08-27 13:23:17 +0000 Debug: UIAButton could not be tapped
      
info: [debug] Socket data received (58 bytes)
info: [debug] Socket data being routed.
info: [debug] Got result from instruments: {"status":13,"value":"elementId 32 could not be tapped"}
info: [debug] Responding to client with error: {"status":13,"value":{"message":"An unknown server-side error occurred while processing the command.","origValue":"elementId 32 could not be tapped"},"ses
sionId":"7f5c7061-48c8-4a7f-b9cc-85c9890f5ab2"}
info: <-- POST /wd/hub/session/7f5c7061-48c8-4a7f-b9cc-85c9890f5ab2/element/32/click 500 351.191 ms - 201
info: [debug] [INST] 2014-08-27 13:23:17 +0000 Error: VerboseError: elementId 32 could not be tapped
      
info: [debug] [INST] 2014-08-27 13:23:17 +0000 Error: Error during eval: tapById@file:///Users/jp.nogueira/Documents/Automation/appium/79F5F4F4-C471-4D86-90C5-11F0CE3E50D2/gesture-ext.js:23:25

       eval code
eval@[native code]

startProcessing@file:///Users/jp.nogueira/Documents/Automation/appium/3FA0666C-CED8-4958-AA32-2477E13CCEFA/commands.js:186:30
bootstrap@file:///Users/jp.nogueira/Documents/Automation/appium/959CB674-E233-416B-86D5-855C80E49360/bootstrap.js:18:29
global code@file:///Users/jp.nogueira/Documents/Automation/appium/4A5F8838-67E5-4E84-A9B7-08A8F36CA8F6/bootstrap-395beb83c59ce844.js:9:10

info: [debug] [INST] 2014-08-27 13:23:17 +0000 Debug: responding with:
      
info: [debug] [INST] 2014-08-27 13:23:17 +0000 Debug: Running system command #115: /usr/local/Cellar/node/0.10.30/bin/node /Users/jp.nogueira/Documents/Automation/appium/node_modules/appium-uiauto/bin/
command-proxy-client.js /tmp/instruments_sock 2,{"status":13,"value":"elementId 32 could not be tapped"}...

So instruments returns exactly the same thing for both requests (apart from the ID which increments every time, I think that is fine):
button("button menu") info: [debug] Got result from instruments: {"status":0,"value":{"ELEMENT":"31"}}
find_element(:name, "button menu") info: [debug] Got result from instruments: {"status":0,"value":{"ELEMENT":"32"}}

Then both use the same method to tap the element but one fail and the other works fine...

Looking at the log file created (info: [debug] [INST STDERR] 2014-08-27 14:23:17.003 ScriptAgent[48146:3007] Log written to /Users/jp.nogueira/Library/Application Support/iPhone Simulator/7.1-64/Library/Logs/CrashReporter/UIALogs/ScriptError-2014-08-27-142317.plist) I can't see any useful info:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>AutoSubmitted</key>
    <true/>
    <key>bug_type</key>
    <string>177</string>
    <key>description</key>
    <string>
VerboseError: UIAButton could not be tapped on line 9223372036854775808 of source


Date/Time:  2014-08-27-142317
Device:  iPhone Simulator(iPhone Simulator:39325d68d672569ba0a94c4f3357bbaa00000000)
OS/Build:  7.1(11D167)

Backtrace:
#0 tap() at
#1 tapById() at :14

Patience Timeout:  (null)
</string>
    <key>displayName</key>
    <string>ScriptError</string>
    <key>name</key>
    <string>ScriptError</string>
    <key>os_version</key>
    <string>7.1(11D167)</string>
    <key>version</key>
    <string></string>
</dict>
</plist>

Any idea? Sorry the long post, but this is blocking me...

Thanks a lot.

[ksh...@savingstar.com]

I am having the exact same issue while running Appium 1.2.1 on my Mac OS 10.9.4 version.

Can anyone think of other suggestions, workarounds ?

[ksh...@savingstar.com]

On Thursday, August 28, 2014 11:20:14 AM UTC-4, ksh...@savingstar.com wrote:

I am having the exact same issue while running Appium 1.2.1 on my Mac OS 10.9.4 version.

Can anyone think of other suggestions, workarounds ?

Is there any solution for this issue?  When will this bug be fixed?

    Here are the details for what I am seeing:

      <?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>AutoSubmitted</key>

<true/>

<key>bug_type</key>

<string>177</string>

<key>description</key>

<string>

VerboseError: UIAElement could not be tapped on line 9223372036854775808 of source

Date/Time:  2014-09-02-122953

Device:  iPhone Simulator(iPhone Simulator:d325a052ff8e54c1869c23d305990c7800000000)

OS/Build:  7.1(11D167)

Backtrace:

#0 tap() at 

#1 tapById() at :14

Patience Timeout:  (null)

</string>

<key>displayName</key>

<string>ScriptError</string>

<key>name</key>

<string>ScriptError</string>

<key>os_version</key>

<string>7.1(11D167)</string>

<key>version</key>

<string></string>

</dict>

</plist>

-------------------------------------

info: [debug] [INST] 2014-09-02 16:29:53 +0000 Debug: evaluating au.tapById('3')

       

info: [debug] [INST] 2014-09-02 16:29:53 +0000 Debug: UIAElement.tap()

       

info: [debug] [INST] 2014-09-02 16:29:53 +0000 Debug: UIAElement could not be tapped

       

info: [debug] [INST STDERR] 2014-09-02 12:29:53.611 ScriptAgent[4415:2f07] Log written to /Users/kshieh/Library/Application Support/iPhone Simulator/7.1-64/Library/Logs/CrashReporter/UIALogs/ScriptError-2014-09-02-122953.plist

[ksh...@savingstar.com]

I am also changed to the latest Appium version and the latest selenium webdriver version: 2.42.0  and I am still seeing the same issue.

This is blocking me also.

[odqwis]

Hey!

I think I fixed my problem which was quit similar to yours - well is more a workaround than a fix. So, since version 1.2.0 appium is returning more element that I actually have in the app - bug reported - some of them with the same name/label/whatever... So what I did was just create a method that searches for elements and returns only the visible ones (if available) for a certain criteria. That fixed the problem, and probably wont be a problem once appium fix that issue as well.

Let me know if you need more help, more than happy to help.

P.

[ksh...@savingstar.com]

The Element I am try to click on is in UIAWindow. It performed isDisplayed check on the element and it says it's visible.

But... when I attempt to click on it, still getting the same error.

name: button_login
type: UIAElement
value:
label: button_login
enabled: true
visible: false
valid: true
location: {20, 359}
size: {280, 44}
xpath: //UIAApplication[1]/UIAWindow[1]/UIAElement[1]


Calling:
    WebElement JFFWindowBtn = sDriver.findElement(By.name("button_login"));

Not sure - what else I can try? Any thoughts?