Cannot craft on Android version running on Intel/x86 processor

Same, I am not using any packs! I've deleted all of my packs and tried, yet it still doesn't work.

If you are using a physical tablet/phone device, can you provide the device model and Android version?
If you are on bluestacks, can you provide the same information if possible?

Asus ZenPad S8.0 Z580CA P01MA android 6.0.1

(unfortunately worlds are stored on application space and cant transfer to new device due to MCPE-85798)

Also tried installing Bluestack 4.270.0.1053 Google Pixel 2XL Running Nougat 32 bit.

Crafting is not possible from crafting table with multiple items there, but Shift + Click is creating the multi-item items on Bluestack.

I have more info and hope it can help staff fixing this issue. The bug happened to me one time.

• After I reinstall Minecraft, the problem gone and I can craft again but as soon as I change the HUD style from Pocket to Classic style the bug happened again and it stay bugged even though I set the HUD style back to Pocket Style.

• I can still craft the Recipe which don't need crafting table, but yet I have to craft them on crafting table, It looks like the first 4 slot of crafting grid is misaligned I need to rearrange basic crafting to following 4 Slots Image for Explanation

I'm using Realme 5A(Android 10) Phone and Bluestack 4.250.0.1070 (Nougat 32 bit)

Additional instances of this bug from a mobile user:

This also happened to my acct but my game is installed on a second device. And note that I am not using Beta Version.

My daughter has the same issue on Asus ZenPad S8.0 Z580CA P01MA android 6.0.1 too

If you are experiencing this issue do you also experience MCPE-121068?

Possibly as the torches look different from usual

Yes.  I never included that in the original bug report as I felt the crafting was more important.

Probable that most, if not all, devices experiencing this (cannot craft) issue also experience MCPE-121068, but not all who experience MCPE-121068 experience this (cannot craft) issue.
Until Mojang figures out what is causing the issue I recommend continuing to provide device details (device model, and possibly Android version?). I assume most, if not all, BlueStacks users experience this issue, but if you as a BlueStacks don't experience this (but they probably won't be here in the first place), please provide your BlueStacks emulated device model and Android version. This advice has not been reviewed by Mojang. Any further advise by Mojang or Mojira staff should be followed as such.
If you have workarounds you can post them here.

HP Zbook laptop:  windows 10

Bluestacks: 4.270.0.1053

Hope this helps.

Lenovo YT3-X90F on android 6.0.1

I'm also experiencing MCPE-121068.

Dell Inspiron 13 7000, running Windows 10

Bluestacks v4.260.20.4001 64-bit Android

I think it should be assumed that all BlueStacks users encounter the issue. If you use BlueStacks but don't, please comment, else I don't think there is a need for BlueStacks users to add their device details.

Tablet Android 5.1

Modelo i15-TFL

O mesmo problema, não consigo craftar a bancada de trabalho na 1.16 pra cima e ao conseguir baixar o Minecraft 1.14 foi possível construir itens e etc.

Android 7.1.1

Table Lenovo Yoga Book YB1-X90F

It seems, in addition to BlueStacks, older Android versions are affected. Can anyone confirm that?

Based on the comments above and duplicate links these are the affected devices so far:

(Android version) Device model
(6.0.1) Asus ZenPad S8.0 Z580CA P01MA
(10) Realme 5A
(6.0.1) Lenovo YT3-X90F
(5.1) Cube iWork10 Ultimate (i15-TFL) ^
(6.0.1) RCA (RCT6873W42) 7" Android Voyager
(7.1.1) Table Lenovo Yoga Book YB1-X90F

^ Unclear if physical or emulator

This seems to be an issue with Intel (Atom?) devices, at least for Android.

All BlueStacks users are presumed to be affected.

How long does it take generally for the issue to be resolve by Mojang? are we speaking weeks or months? Thanks

I am seeing this with v1.16.210 on an ASUS Zenpad S Z580C (Intel processor) running Android 6.0.1. This broke immediately after the latest patch update. Reset the application cache, then data, then reinstalled Minecraft completely and no luck. Also seeing MCPE-121068.

Really disappointing that this issue has been seen since February 7 and still no resolution.

LenovoPad YOGA Tablet 2-830LC Android Ver 5.0.1

I'm not using bluestacks

When I first reported this issue back on Feb 7th I found three issues. The crafting issues, the pixel issue and mining underwater which would freeze the game and I would have to reload Minecraft to find myself drowned. I reported just the crafting due to it being the most important.  Is the third issue related too?  To answer the question posed is this affecting older android models also... As reported in my original ticket, I could NOT get past the 'Lets go' screen on my old Samsung galaxy A elite thus bought it again using bluestacks .  In defense for Bluestacks .. As originally stated I did load that account on bluestacks and it did fix the 'Lets go' startup problem tho the crafting issue remained.  <side note: That now runs on my old android. Bluestacks fixed that problem for me. Granted its not Beta and will never be beta so I have a playable version of Minecraft to play.>  In answer to how long does it take to resolve an issue .. in this matter we are all waiting for that answer. As seen the here they are working on the matter very seriously.  In past issues, my Son has gotten issues resolved in a matter of a week. 

Final thoughts: Thank you everyone for your comments and support in bringing this issue to light. Your comments help the Mojang staff to better resolve these issues and make a better playing environment for us all. 

To Mojang studios: We support your efforts and though sometimes we may be discouraged we also know you are working hard to  resolve our issues.  Thank you.

For Bedrock Edition, we generally do not really know how long Mojang takes to fix issues. For issues like these which seriously impede gameplay, my guess is that they likely get prioritised something similar to "Very Important" (let's pretend this is the highest priority) or at the very least "Important" in their internal bug tracker (the ADO is the ticket number in that tracker), which mean they tend to be resolved quicker.
However it will depend on how quickly Mojang can identify the offending code, which varies from instantly obvious to very difficult, or they identify the code but a large part needs to be rewritten to fix it. The best we get on updates is if a Moderator on this side gets feedback from the Mojang staff or a fix version is applied. It also sometimes helps if we can provide them more information on technical setup, game settings, caveats etc.
My guess is that since the ADO was only assigned 4 days ago, this may or may not be fixed in 1.16.220, but it is also possible a hotfix like 1.16.221 might be released (don't quote me, it's a guess), or it will be fixed in 1.16.230. I don't know the code, however, so it could also take longer.

In short: higher priority -> tends to be fixed faster, less offending code -> tends to be fixed faster, when will it be fixed -> take an educated guess
Oh, and more votes. More votes means Mojang knows it affects more people.

Anyways, for the mining crash issue, if the crash is consistently reproducible using certain steps, you can search for the bug and if it doesn't exist, report it. Not sure if it's directly related, caused by a confounding factor, or something else.

In case it's helpful to anyone, there is a work-around:

1. Locate the item you'd like to craft in the recipe book

2. To craft one of the item, right-click on it in the recipe book.

3. To craft as many of the item as your current inventory permits, +Shift + left-click+ on the item in the recipe book

I get the same thing on version 1.16.210 guess its back to 1.16.201

i have the same problem, i installed the game yesterday over bluestacks and i can´t craft anything

I have the exact same issue. Trying to play over BlueStacks and I can’t craft at all. VERY frustrated 

Definitely has something to do with the android x86 platform.  

EDIT: Booted up an android x86 vm running android nougat to simulate bluestacks, and am unable to craft and experiencing the texture glitches 

Is this still an issue in 1.16.220/1.16.230.56 beta?

Yes this is still an issue using Bluestacks. Just updated and tried it. 

It's not just Bluestacks related; having the same (at least very similar) problem on Android devices.

issue still there for android and version 1.16.221

@Riko Are you talking about x86 android, because, this issue isnt present on 32 bit and 64 bit android devices, I tested it on devices running android 7 and above, also, I'm talking about mobile devices/tablet devices running android, not the x86 version or an emulator on x86, also this is an x86 only bug,since using the minecraft bedrock linux launcher on my raspberry pi 3B+ running both 32 and 64 bit OS, I dont get this issue... (I'm not saying all I say is correct, but, I just wanted to get a clarity, and sorry for the unnecessarily long comment 😞 )

Yes still unresolved on my daughter tablet Asus ZenPad S8.0 Z580CA P01MA android 6.0.1 

...and on both of my daughters' Hudl 2 android tablets (and not on my Windows 10 bedrock app).

I can confirm these issues are NOT affecting Win 10 bedrock <Both Normal play and Beta> using the 'SAME' laptop they are affecting  when using bluestacks.

Affected Platforms (will keep updated):

• Some Android devices (possibly Intel Atom)

• All PC emulator users

Agree. Windows 10 unaffected. Android tablet is also a complete bust, in addition to bluestacks (and the 'right click', 'left click' workaround isn't relevant as there isn't such a concept on an android touch device).

The culprit appears to be Android x86 compatibility. As a result, this affects all Android emulators for PCs that are not using ARM processors (tested using emulators other then Bluestacks). There is no easy workaround for this (unless you're willing to pay $27 USD for the Windows 10 Store version of the game).

Whilst we're waiting on a fix, I managed to craft a couple of things by putting items in different places.
Torch

Crafting table

Coarse Dirt

Thanks to Dan Singh's post, I think Ive found a pattern. Ive attached a diagram.

I think its important to note that some of the recipes that work with this method don't allow picking up the resulting item. I'm not really sure what the logic is behind what can and cannot be picked up though.

A (very incomplete) list of craftable items:

crafting table (resists pickup)
torch (resists pickup)
quartz block (resists pickup)
button (can pick up)
shears (resists pickup)
flint and steel (can pick up)
mushroom stew (can pick up)
iron nugget (can pick up)

Thank you for these helpful comments and for the time you gave to find them.

I have tried on LDPlayer 4, Nox Player, and Lineage OS on virtualbox but no go. I still have the pixel offset by 1 and inability to craft in each one.

Since the issue appears to affect only shaped recipes (must be put in a certain order), a quick and dirty workaround would be to create a behaviour pack that changes all recipes to shapeless recipes. Some recipes which have the same ingredients but different order will need to be changed if using this proposed workaround.

Come on Mojang!!! Minecraft is completely broken on a large segment of hardware (Intel based Android devices). It has been almost FOUR MONTHS. How could you not see this as a priority to fix?

Mojang usually doesn't give updates on a bug, as most of their work is done in their internal bug tracker. The bug is already in their internal tracker; the ADO is the corresponding ticket number. Since this bug effectively breaks the game, Mojang has probably assigned a high priority to this issue internally. An serious bug that hasn't been fixed for a long time, in my opinion, means that they have found it difficult to locate the issue or create a fix (if anyone has a workable fix or pointer, feel free to comment).
If someone would like to spend some time "deshaping" the recipes (as my previous comment), please feel free to do so.

Is there possibility to install earlier version of Minecraft without this bug?

@unknown Not officially.

I really wish I knew about this issue before buying MCPE. I was'nt able to get a refund 😞 

It's completely useless with the bug. Android Yogabook YB1-X90F.  Yes, its an older device, but it still works great, Well, for most apps. 

Found a workaround for Bluestacks Users.

First of all, this bug and MCPE-121068 doesn't appear when you use nougat 32-bit. 

Once you are using the 32-bit installation, change your ABI settings to ARM.

If you already have minecraft installed, you may need to reinstall it.

I have also been having this issue and reported it. until fixed you need to place a crafting table down put all but needed items for crafting items out of personal inventory such as only one stick and two diamonds in inventory. When you goto crafting a diamond sword it shows up red on the crafting table, but if hold the shift button on an item on the inventory of the crafting table, not the red one, it will create the item in your inventory. The only problem is you need the exact amount of materials you want to make the amount you want, otherwise, you end up using all inventory to max produce item attempting. I made a whole stack of crafting tables by shifting my first time, instead of crafting just one, and the same with a wooden pick ax. It is a pain but a temporary solution while playing. I play hardcore survival rules and it is not easy.

My boyfriend got this issue as well since this Wednesday mid-game a few hours after we updated it with the 1.17.0 version (I usually play on an Xbox One and it didn't happen to me, it's pretty normal still). He plays on MSI bluestacks so today I got it as well for my pc to see if it was working and I got the same issue; couldn't craft anything with more than one item.

I haven't tried it yet on my phone (Android J6) but once I do, I can edit this here.

My daughter is also seeing this on her Tesco Hudl 2, like someone else above. And just like the others, this is an Intel Atom tablet.

I'm puzzled as to why it's taken 5 months (so far) to address a bug that renders this product fundamentally unusable for what must be a significant number of customers. I can confirm I've experienced MCPE 12106. I'll add that I've had this issue (117105) using both bluestacks and Nox player, and I know of another user experiencing the issue on their android phone. I haven't checked to see if I'm experiencing 12106 on Nox. Can't use the nougat 32-bit instance manager fix as i'm on a mac.

this seems to be some sort of x86/amd64 processor issue for the android version of pocket. i can confirm for pop_os in an intel core i3 (dont ask me how i got bedrock edition on linux, its basically the android version :/) but it has the same issue as bluestacks or nox.
A workaround for this issue is have the recipe book open at all times and use right mouse button to craft. this will craft only 1 of the item you select without needing to use the grid.

can confirm this in the android launcher of Linux running KDE Neon, also happens when using Anbox

I am having this problem playing through bluestacks, whats strange is that my friend who plays on PS4 was also having this issue after 1.17 update.

Im havin the same issue. When i play on a minecraft client that allows you to play on Linux and Mac (its using android), crafting dosent work. the only workaround is to use the recipe book.

Thank you for finally fixing this insane gameplay bug on my Android x86_64 based device in 1.18.0.24 both x86 and x86_64 versions. It is still fixed in 1.18.0.25. I'm looking forward to see the first stable release of 1.18, without crafting and texture bugs.
The related texture issue MCPE-121068 is fixed in the exact same version.

I have no idea why this bug appeared in 1.16.210 or why it took ca. 11 month to fix. I cannot find anything about this in the official Changelog https://feedback.minecraft.net/hc/en-us/articles/4412150636941-Minecraft-Beta-1-18-0-24-Xbox-One-Windows-10-Android-

I've made a bit of a discovery

Using x86 emulators on ARM-based devices (such as the Surface Pro X) has this issue, but using a native ARM Android emulator on a Surface Pro X does not show this issue (tested on 1.18.0.25)

update: this issue is now fixed on release 1.18.

Please comment if you still experience this bug in the latest version.

This does still occur in 1.18.2 and 1.18.10.22.

This bug is fixed with v1.18.2 on an ASUS Zenpad S Z580C (Intel processor) running Android 6.0.1.

Affects 1.18.20.25