Status Update
No update yet.
Comments
jp...@google.com
cm...@gmail.com
thanks for create this issue instance. It is more related to generated Binding Class in Data Binding is deemed to be Unresolved by KT Editor, when multiple base modules in the project has the same Data Binding classes.
cm...@gmail.com
The bar for cherry picking is too high, I'm afraid. If I understand things correctly...
- The workaround is simple (just ignore it for now)
- This isn't a regression, it's been present in older versions of Studio
- (As far as our team can tell) this doesn't affect a large % of all Studio users
If these are true, then it's certain the request for a cherry pick will be rejected. After all, cherry picks are risky (landing so late) and require a bunch of resources (an additional test path with QA brought up to speed), so I've seen worse bugs rejected for cherry picks than something like this.
Let me know if I'm missing anything. I'm closing this bug down for process reasons, but please feel free to keep the conversation going and I'll respond.
cm...@gmail.com
I think it is fine to leave the status: Won't fix for this issue instance, since the fix is in 4.2 Canary 9 already.
- The workaround is simple (just ignore it for now)
- This isn't a regression, it's been present in older versions of Studio
not an objection for me as the issue reporter.
(As far as our team can tell) this doesn't affect a large % of all Studio users
I think it is really an edge case. As far as i can think of the scenarios to cause this happen would be:
- Doing the Android Kotlin Codelabs, since it happens a lot to duplicate the base module as
finalandstartfor scaffolding learning - Working with the App solution across multiple android based devices, such as Wear OS, Android phone while the project has multiple base modules all having the same named layout files for features such as SettingsFragment.
When i was able to change the runtime of AS 4.0.1 to OpenJDK 11 with Choose Runtime Plugin. The issue seems to be resolved, but as far as i click on the reference to open the declarations the Android Studio 4.0.1 has crashed and restarted by itself. Such a behaviour doesn't seem to happen in AS 4.1 RC2.
je...@google.com
cm...@gmail.com
Build was succeeds but the IDE shows unresolved references same as the OP. The error is intermittently appeared even I had no change to the related layout file and class that use the generated binding class.
cm...@gmail.com
Thanks for your update, but it's hard to confirm whether it is the same bug since 3 years have passed.
In
The reporter said that this issue has been fixed in Android Studio 4.2 Canary 9
This makes me believe that you are hitting a different issue (different root cause with the same symptom).
Please file a new bug with us with as many details as possible and we can start/restart the investigation process.
cm...@gmail.com
am...@google.com
We have been facing this as well in our team of 5 developers. It is just random and annoying to face this as a developer and we are now using Hedgehog | 2023.1.1 Patch and this hasn't been resolved
cm...@gmail.com
Thanks, to help us debug the issue, could you try and make a reproducible project and attach it here?
am...@google.com
am...@google.com
As
Unfortunately, we can't investigate this issue from screenshots alone. It is most helpful if you can reproduce the issue with resource update tracing enabled. This can be done as follows:
- Open actions search (
Ctrl+Shift+Aon Windows/Linux,⌘+Shift+Aon Mac) - Search for "trace resource updates"
- Click the toggle to turn it on
- Restart Studio.
Then, when the bug happens again, collect the idea.log file. This log file can be found by going to Help > Collect Logs and Diagnostic Data.
I'm re-closing this bug, since there's nothing we can investigate with the attached screenshots. @5, @7, and @8: please file a new bug if/when you run into this and attach idea.log, so that we can investigate the individual root causes.
Description
####################################################
Please provide all of the following information, otherwise we may not be able to route your bug report.
####################################################
1. Describe the bug or issue that you're seeing.
Please refer to open source aTalk project at:
The whole problem started after aTalk migrates i.e. v3.3.0/3.3.1 to support API-34, and with the new SDE setup as shown below (attached SDE - gradle-7.6-bin.zip).
a. The problems happen for aTalk v3.3.0/v3.3.1 releases and only with apk/aab built via Tool menu | Build.
b. Under AS system debug built and via adb install, both release/debug builds DO NOT exhibit the problems.
c. aTalk v3.2.4 and all earlier releases for API-33, and built with AS Eel (gradle-6.9-bin.zip): All aTalk builds are working, and DO NOT exhibit any of the problem reported here.
With aTalk v3.3.0/3.3.1 installed built via [menu | Build]:
All android physical devices, including AVD pixel have many problems e.g.
a. aTalk client is unable to register with the network.
b. Unable to send attached files
c. Unable to use Menu Exit aTalk
d. Most likely many others need to be uncovered.
// ============ Following are the logcat captured for the observed problem ==========/
05:13:35.869 D Adding protocol provider Jabber:swan@atalk.sytes.net
05:13:35.870 E FATAL EXCEPTION: main
Process:
android.content.ActivityNotFoundException: No Activity found to handle Intent { act=org.atalk.show_contacts }
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2239)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1878)
at android.app.Activity.startActivityForResult(Activity.java:5589)
at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:780)
at android.app.Activity.startActivityForResult(Activity.java:5547)
at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:761)
at android.app.Activity.startActivity(Activity.java:6045)
at android.app.Activity.startActivity(Activity.java:6012)
at org.atalk.android.gui.account.AccountLoginActivity.onLoginPerformed(AccountLoginActivity.java:153)
at org.atalk.android.gui.account.AccountLoginFragment.lambda$initButton$3$org-atalk-android-gui-account-AccountLoginFragment(AccountLoginFragment.java:281)
at org.atalk.android.gui.account.AccountLoginFragment$$ExternalSyntheticLambda0.onClick(Unknown Source:4)
at android.view.View.performClick(View.java:7659)
at android.view.View.performClickInternal(View.java:7636)
at android.view.View.-$$Nest$mperformClickInternal(Unknown Source:0)
at android.view.View$PerformClick.run(View.java:30156)
at android.os.Handler.handleCallback(Handler.java:958)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:205)
at android.os.Looper.loop(Looper.java:294)
at android.app.ActivityThread.main(ActivityThread.java:8177)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:971)
// -************* Login problem *************
05:26:09.282 E Failed to register protocol provider.
java.lang.AbstractMethodError: abstract method "void org.jivesoftware.smack.ConnectionListener.connecting(org.jivesoftware.smack.XMPPConnection)"
at org.jivesoftware.smack.AbstractXMPPConnection.callConnectionConnectingListener(AbstractXMPPConnection.java:1693)
at org.jivesoftware.smack.AbstractXMPPConnection.connect(AbstractXMPPConnection.java:516)
at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.connectAndLogin(ProtocolProviderServiceJabberImpl.java:1206)
at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.initializeConnectAndLogin(ProtocolProviderServiceJabberImpl.java:871)
at net.java.sip.communicator.impl.protocol.jabber.ProtocolProviderServiceJabberImpl.register(ProtocolProviderServiceJabberImpl.java:728)
at net.java.sip.communicator.util.account.LoginManager$RegisterProvider.run(LoginManager.java:316)
// -************* send file error *************
06:00:48.827 E FATAL EXCEPTION: AsyncTask #2
Process:
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$4.done(AsyncTask.java:415)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:381)
at java.util.concurrent.FutureTask.setException(FutureTask.java:250)
at java.util.concurrent.FutureTask.run(FutureTask.java:269)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:305)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)
Caused by: java.lang.AbstractMethodError: abstract method "javax.xml.namespace.QName org.jivesoftware.smack.packet.FullyQualifiedElement.getQName()"
//===========================
2. Attach log files from Android Studio
2A. In the IDE, select the Help..Collect Logs and Diagnostic Data menu option.
2B. Create a diagnostic report and save it to your local computer.
2C. Attach the report to this bug using the Add attachments button.
see attached.
3. If you know what they are, write the steps to reproduce:
3A. Download aTalk version 3.3.1 from
3B. Set Build Variant PlayStoreDebug
3C. Using AS giraffe, Debug 'aTalk' -> build and install via adb to device; everything work OK without any problem
3D. Via Tool menu | Build the aTalk-playstore-debug,apk
3E. Drag and drop to AVD to install. You will see all the reported problems in this comment.
The observed problems are very serious as the aab release into the playstore has completely different behaviour as compared to the apk installed via Debug build. Kindly investigate and provide a solution.
In addition to logs, please attach a screenshot or recording that illustrates the problem.
For more information on how to get your bug routed quickly, see
Build: AI-223.8836.35.2231.11005911, 202310260919
AI-223.8836.35.2231.11005911, JRE 17.0.6+0-17.0.6b829.9-10027231x64 JetBrains s.r.o., OS Linux(amd64) v6.5.0-14-generic, screens 3840.0x2160.0, 2560.0x1600.0
AS: Giraffe | 2022.3.1 Patch 3
Kotlin plugin: 223-1.9.0-release-358-AS8836.35.2231.11005911
Android Gradle Plugin: 7.4.2
Gradle: 7.6
Gradle JDK: Oracle OpenJDK version 15.0.2
NDK: from module: 22.1.7171670, from local.properties: (not specified), latest from SDK: 26.1.10909125
CMake: from local.properties: (not specified), latest from SDK: 3.22.1-g37088a8, from PATH: 3.22.1
```